Server Timeout Accessing a Formview

[aradia926]

I've built a custom web-based CRM in ASP.NET 2.0 on Sql Server 2000.

Currently updating a contact is very inconsistent. If I go into a contact through

http://MyServer/secure/allcontacts.aspx

or

http://MyServer/secure/allcontacts.aspx?contactid=6151

then the updatecontact() sub that I have defined runs fine.

UpdateContact() consists of a sql server transaction with a try/catch block and parameters for each field on the page.

If I go through

http://MyServer/secure/allcontacts.aspx?contactid=6151&Dup=true

then I get

"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding,"

on the catch section but no error message is rendered to the user - they see nothing at all. This seems to be happening when the application tries to access a formview control (which may or may not be visible at the time).

I've tried Data.SqlClient.SqlConnection.ClearAllPools(), myCommand.CommandTimeout = 3000, and <httpRuntime executionTimeout="180"/> in the web.config but none of these seems to be working.

The formview has a sql datasource and it gets as far as running the sqldatasource_selecting event and then gets stuck.

Can anyone help me figure out why this is happening and how I can fix it?

Thanks in advance.

 

[dvannoy]

did you increase the "Query Timeout" on the sql server itself?

how busy is that server?

what does this &amp;Dup=true refer to?

is your transaction a SP?

 

[aradia926]

I set the Query Timeout on the sql server to 0 (unlimited).

I wouldn't say the server is very busy. It is an internal application that is only accessed by 25 people and maybe an average of 7 concurrently.

When the user performs a search to determine if the contact record that they are trying to enter already exists and that search comes back with a duplicate, &amp;Dup=true is appended to the querystring. Instead of allowing the user to enter the record, it redirects the user to the existing record and allows them to edit it.

My transaction is not a SP, it just resides in the code.

Does that help?

 

[dvannoy]

OK, so it times out before the "Editable" Record appears correct? or does it time out when the user tries to update the record?

post your code.