:confused:Time Out Error??
-
Hi all, One of my applications on the intranet is giving the following error... "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ASP.createrequest_aspx.updateTable() in C:\web\capexrequest\createrequest.aspx:line 737" The application was running fine until earlier today and suddenly this error..I have no clue what it is... if it has something to do with connectivity then I am using executereader() and Connection.close().also, all my other applications pretty much similar rather exactly similar are working fine except this one...:~ Can some one help? Thanks in advance Aartee. ...HE is watching Us All!
-
Hi all, One of my applications on the intranet is giving the following error... "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ASP.createrequest_aspx.updateTable() in C:\web\capexrequest\createrequest.aspx:line 737" The application was running fine until earlier today and suddenly this error..I have no clue what it is... if it has something to do with connectivity then I am using executereader() and Connection.close().also, all my other applications pretty much similar rather exactly similar are working fine except this one...:~ Can some one help? Thanks in advance Aartee. ...HE is watching Us All!
Accordin to the error message, you're not getting a response from the SQL server within the default command timeout (30 seconds, I think!) This is usually because whatever SQL code your server is executing is taking forever to return anything. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
Accordin to the error message, you're not getting a response from the SQL server within the default command timeout (30 seconds, I think!) This is usually because whatever SQL code your server is executing is taking forever to return anything. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
Thankyou Dave, yes I have resolved the issue..I had not closed the connection in pageload. actually, i open and close the connection in several places in my application. your help is much appreciated, thankyou. Aartee. ...HE is watching Us All!
-
Thankyou Dave, yes I have resolved the issue..I had not closed the connection in pageload. actually, i open and close the connection in several places in my application. your help is much appreciated, thankyou. Aartee. ...HE is watching Us All!
That would explain it. If you don't close the connection, the number of connections being used on the SQL server increases until it hits the license limit. Then you next connection request will hang until a previous connection is closed, thereby causing the timeout. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome