|
Home > Archive > MS SQL Server > July 2005 > Re: New problem w/ Timeout Expired
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: New problem w/ Timeout Expired
|
|
| David Gugick 2005-07-05, 8:23 pm |
| Matt C. wrote:
> Starting today, an application that has previously run without
> problems (for several weeks now) has started throwing Timeout Expired
> errors after 30 seconds.
>
> The Command.CommandTimeout, Connection.CommmandTimeout, and
> Connection.ConnectionTimeout on the client are all set properly to
> values well in excess of 30 seconds. Also, the Connection object is
> using adUseServer.
>
> The application was developed using the SQLOLEDB provider. I have
> made a test version using the MSDASQL.1 provider, and this test
> version seems to be running OK. So there is some problem with the
> SQLOLEDB provider, apparently. (Using MSDASQL for testing is fine,
> but I do not want to switch db providers permanently unless there is
> no other choice.)
>
> We use Windows Update on our servers and workstations, and the
> spontaneous nature of this problem makes me wonder if WU is to blame.
>
> Has anyone had similar experiences? Other ideas about what's
> happening?
>
> Matt
That sounds a lot like you are experiencing lock timeouts. Do you have a
lock timeout set for your connections using SET LOCK_TIMEOUT? The
default is -1 (infinite).
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
| |
| Matt C. 2005-07-05, 8:23 pm |
| "David Gugick" <david.gugick-nospam@quest.com> wrote in
news:eKO#snagFHA.3692@TK2MSFTNGP09.phx.gbl:
> That sounds a lot like you are experiencing lock timeouts. Do you have a
> lock timeout set for your connections using SET LOCK_TIMEOUT? The
> default is -1 (infinite).
Thanks for the response.
No, the app doesn't set that, and running SELECT @@LOCK_TIMEOUT from QA
returns -1.
Matt
| |
| David Gugick 2005-07-05, 8:23 pm |
| Matt C. wrote:
> "David Gugick" <david.gugick-nospam@quest.com> wrote in
> news:eKO#snagFHA.3692@TK2MSFTNGP09.phx.gbl:
>
>
> Thanks for the response.
>
> No, the app doesn't set that, and running SELECT @@LOCK_TIMEOUT from
> QA returns -1.
>
> Matt
Do any of your stored procedures set the lock timeout internally?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
| |
| Matt C. 2005-07-06, 9:23 am |
| "David Gugick" <david.gugick-nospam@quest.com> wrote in news:
##uisAbgFHA.1044@tk2msftngp13.phx.gbl:
> Matt C. wrote:
>
> Do any of your stored procedures set the lock timeout internally?
No, they sure don't. I've doublechecked, even.
Matt
|
|
|
|
|