| Groups | Blog | Home |
dotnet ado.net : It's back - the timeout problem
One of our testers is getting this now - and he is not running under a debugger. The error is: Exception(s):DataSourceException: executeQuery select=select CategoryName from Categories Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. It occurs randomly. And it returns this in under a second so it's unlikely to be an actual timeout. Also this is hitting Sql Server 2005 Express on the user's computer so it can't be a network issue. Any idea what this can be? This code is called when clicking a button in our program which then runs the exact same code each time. This happens occasionally and when it does sometimes it happens again the next 2 or 3 times we click the button and then it's gone and everything is working. -- thanks - dave david_at_windward_dot_net http://www.windwardreports.com Cubicle Wars - http://www.windwardreports.com/film.htm
Single threaded connnection (static connection object)
Too short of a timeout setting Error in the code (cannot tell, as I see none) -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA http://gregorybeamer.spaces.live.com Co-author: Microsoft Expression Web Bible (upcoming) ************************************************ Think outside the box! ************************************************ [quoted text, click to view] "David Thielen" <thielen@nospam.nospam> wrote in message news:E1629717-20EE-4241-8A75-8594BDC75A34@microsoft.com... > Hi; > > One of our testers is getting this now - and he is not running under a > debugger. The error is: > Exception(s):DataSourceException: executeQuery select=select CategoryName > from Categories Timeout expired. The timeout period elapsed prior to > completion of the operation or the server is not responding. > > It occurs randomly. And it returns this in under a second so it's unlikely > to be an actual timeout. Also this is hitting Sql Server 2005 Express on > the > user's computer so it can't be a network issue. > > Any idea what this can be? This code is called when clicking a button in > our > program which then runs the exact same code each time. This happens > occasionally and when it does sometimes it happens again the next 2 or 3 > times we click the button and then it's gone and everything is working. > > -- > thanks - dave > david_at_windward_dot_net > http://www.windwardreports.com > > Cubicle Wars - http://www.windwardreports.com/film.htm > >
Hi;
Thanks for the ideas. I looked at each: [quoted text, click to view] > Single threaded connnection (static connection object) Definitely not this.[quoted text, click to view] > Too short of a timeout setting We do not set the timeout so it's the default. And this happens immediately while connections that succeed can take a half second to several seconds and those work. [quoted text, click to view] > Error in the code (cannot tell, as I see none) That's my guess too - but we have been over it and over it. And the code is very straightforward. -- thanks - dave david_at_windward_dot_net http://www.windwardreports.com Cubicle Wars - http://www.windwardreports.com/film.htm [quoted text, click to view] "Cowboy (Gregory A. Beamer)" wrote:
> Single threaded connnection (static connection object) > Too short of a timeout setting > Error in the code (cannot tell, as I see none) > > -- > Gregory A. Beamer > MVP; MCP: +I, SE, SD, DBA > http://gregorybeamer.spaces.live.com > Co-author: Microsoft Expression Web Bible (upcoming) > > ************************************************ > Think outside the box! > ************************************************ > "David Thielen" <thielen@nospam.nospam> wrote in message > news:E1629717-20EE-4241-8A75-8594BDC75A34@microsoft.com... > > Hi; > > > > One of our testers is getting this now - and he is not running under a > > debugger. The error is: > > Exception(s):DataSourceException: executeQuery select=select CategoryName > > from Categories Timeout expired. The timeout period elapsed prior to > > completion of the operation or the server is not responding. > > > > It occurs randomly. And it returns this in under a second so it's unlikely > > to be an actual timeout. Also this is hitting Sql Server 2005 Express on > > the > > user's computer so it can't be a network issue. > > > > Any idea what this can be? This code is called when clicking a button in > > our > > program which then runs the exact same code each time. This happens > > occasionally and when it does sometimes it happens again the next 2 or 3 > > times we click the button and then it's gone and everything is working. > > > > -- > > thanks - dave > > david_at_windward_dot_net > > http://www.windwardreports.com > > > > Cubicle Wars - http://www.windwardreports.com/film.htm > > > > > >
Hi,
This error occurs when a database query or stored procedure is not able to complete execution before a pre-set timeout period expires.I would suggest try all the suggestions given in below link.It might solve your problem. http://www.ironspeed.com/Designer/4.3.0/WebHelp/Part_VI/Timeout_expired_The_timeout_period_elapsed_prior_to_completion.htm -- Hope this helps. Thanks and Regards. Manish Bafna. MCP and MCTS. [quoted text, click to view] "David Thielen" wrote:
> Hi; > > One of our testers is getting this now - and he is not running under a > debugger. The error is: > Exception(s):DataSourceException: executeQuery select=select CategoryName > from Categories Timeout expired. The timeout period elapsed prior to > completion of the operation or the server is not responding. > > It occurs randomly. And it returns this in under a second so it's unlikely > to be an actual timeout. Also this is hitting Sql Server 2005 Express on the > user's computer so it can't be a network issue. > > Any idea what this can be? This code is called when clicking a button in our > program which then runs the exact same code each time. This happens > occasionally and when it does sometimes it happens again the next 2 or 3 > times we click the button and then it's gone and everything is working. > > -- > thanks - dave > david_at_windward_dot_net > http://www.windwardreports.com > > Cubicle Wars - http://www.windwardreports.com/film.htm >
Hi,
Actually System.Data.IDbCommand.CommandTimeOut = 50; as given in link is not working.What you can do is inrease commantimeout of command object to higher value say 120.And also increase executiontimeout in web.config.Let me kmow if these things have solved your problem.Most importantly you must try to figure out why the query or stored procedure is running slow ny using SQL Profiler.Try creating appropriate index or if possible try to return fewer records. -- Hope this helps. Thanks and Regards. Manish Bafna. MCP and MCTS. [quoted text, click to view] "David Thielen" wrote:
> Hi; > > One of our testers is getting this now - and he is not running under a > debugger. The error is: > Exception(s):DataSourceException: executeQuery select=select CategoryName > from Categories Timeout expired. The timeout period elapsed prior to > completion of the operation or the server is not responding. > > It occurs randomly. And it returns this in under a second so it's unlikely > to be an actual timeout. Also this is hitting Sql Server 2005 Express on the > user's computer so it can't be a network issue. > > Any idea what this can be? This code is called when clicking a button in our > program which then runs the exact same code each time. This happens > occasionally and when it does sometimes it happens again the next 2 or 3 > times we click the button and then it's gone and everything is working. > > -- > thanks - dave > david_at_windward_dot_net > http://www.windwardreports.com > > Cubicle Wars - http://www.windwardreports.com/film.htm >
I don't think it is actually timing out because this happens in under a second.
And it is hitting the Northwind database - the standard Microsoft sample. It's well designed and small so I don't think its the DB schema. -- thanks - dave david_at_windward_dot_net http://www.windwardreports.com Cubicle Wars - http://www.windwardreports.com/film.htm [quoted text, click to view] "Manish Bafna" wrote:
> Hi, > Actually System.Data.IDbCommand.CommandTimeOut = 50; as given in link is not > working.What you can do is inrease commantimeout of command object to higher > value say 120.And also increase executiontimeout in web.config.Let me kmow if > these things have solved your problem.Most importantly you must try to figure > out why the query or stored procedure is running slow ny using SQL > Profiler.Try creating appropriate index or if possible try to return fewer > records. > -- > Hope this helps. > Thanks and Regards. > Manish Bafna. > MCP and MCTS. > > > > "David Thielen" wrote: > > > Hi; > > > > One of our testers is getting this now - and he is not running under a > > debugger. The error is: > > Exception(s):DataSourceException: executeQuery select=select CategoryName > > from Categories Timeout expired. The timeout period elapsed prior to > > completion of the operation or the server is not responding. > > > > It occurs randomly. And it returns this in under a second so it's unlikely > > to be an actual timeout. Also this is hitting Sql Server 2005 Express on the > > user's computer so it can't be a network issue. > > > > Any idea what this can be? This code is called when clicking a button in our > > program which then runs the exact same code each time. This happens > > occasionally and when it does sometimes it happens again the next 2 or 3 > > times we click the button and then it's gone and everything is working. > > > > -- > > thanks - dave > > david_at_windward_dot_net > > http://www.windwardreports.com > > > > Cubicle Wars - http://www.windwardreports.com/film.htm > >
Hi,
This totally sounds like a deadlock issue. Some timeouts are not really performance issues but more in the area of scaling or concurrency when a feature is not being used properly or being used without being aware of the consequences or being used unknowingly. Sp_who2 should show a blockage - can be due to a transaction. Can also consider the with nolock option, but sounds like not necessary for that action yet - sounds like a leaky transaction. ref:http://discuss.joelonsoftware.com/default.asp?dotnet.12.505023.22 -- Hope this helps. Thanks and Regards. Manish Bafna. MCP and MCTS. [quoted text, click to view] "David Thielen" wrote:
> I don't think it is actually timing out because this happens in under a second. > > And it is hitting the Northwind database - the standard Microsoft sample. > It's well designed and small so I don't think its the DB schema. > > -- > thanks - dave > david_at_windward_dot_net > http://www.windwardreports.com > > Cubicle Wars - http://www.windwardreports.com/film.htm > > > > > "Manish Bafna" wrote: > > > Hi, > > Actually System.Data.IDbCommand.CommandTimeOut = 50; as given in link is not > > working.What you can do is inrease commantimeout of command object to higher > > value say 120.And also increase executiontimeout in web.config.Let me kmow if > > these things have solved your problem.Most importantly you must try to figure > > out why the query or stored procedure is running slow ny using SQL > > Profiler.Try creating appropriate index or if possible try to return fewer > > records. > > -- > > Hope this helps. > > Thanks and Regards. > > Manish Bafna. > > MCP and MCTS. > > > > > > > > "David Thielen" wrote: > > > > > Hi; > > > > > > One of our testers is getting this now - and he is not running under a > > > debugger. The error is: > > > Exception(s):DataSourceException: executeQuery select=select CategoryName > > > from Categories Timeout expired. The timeout period elapsed prior to > > > completion of the operation or the server is not responding. > > > > > > It occurs randomly. And it returns this in under a second so it's unlikely > > > to be an actual timeout. Also this is hitting Sql Server 2005 Express on the > > > user's computer so it can't be a network issue. > > > > > > Any idea what this can be? This code is called when clicking a button in our > > > program which then runs the exact same code each time. This happens > > > occasionally and when it does sometimes it happens again the next 2 or 3 > > > times we click the button and then it's gone and everything is working. > > > > > > -- > > > thanks - dave > > > david_at_windward_dot_net > > > http://www.windwardreports.com > > > > > > Cubicle Wars - http://www.windwardreports.com/film.htm > > >
I think I found it. We had one place where we were not closing a reader and
connection in one place. That seems to have solved it. It was random so we don't know for sure. Big thank you to the posters here who said that a timeout could actually be a lock on resources. -- thanks - dave david_at_windward_dot_net http://www.windwardreports.com Cubicle Wars - http://www.windwardreports.com/film.htm [quoted text, click to view] "WenYuan Wang [MSFT]" wrote:
> Hello Dave, > > We haven't met such issue before. I'm not sure what is the root cause. > Have you resolved the issue so far? > If it still persists, would you please paste some code snippet? > Therefore, we can perform further analyze. thanks. > > Have a great day, > Best regards, > Wen Yuan > Microsoft Online Community Support > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. >
Hello Dave,
We haven't met such issue before. I'm not sure what is the root cause. Have you resolved the issue so far? If it still persists, would you please paste some code snippet? Therefore, we can perform further analyze. thanks. Have a great day, Best regards, Wen Yuan Microsoft Online Community Support ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
| home · blog · groups | Questions? Comments? Contact the dn |