Recent Timeout Error

[Brian Peddle]

I recently moved hosting companies, we went from a Windows 2000 environment to a Windows 2003 environmennt.

Since the move I have started to get timeout errors about once a day. I maybe got an error like this once every 4 months before the move.

Microsoft OLE DB Provider for SQL Server (0x80040E31)
Timeout expired

It will occur for any page with a query and it can last anywhere from 30 min to 3 hours before it corrects itself.

Has anyone every seen this behavior when switching 2000 -> 2003. Any suggestions for tracking why its happening. I look in the SQL logs and nothing standouts.

[Steven Cheng[MSFT]]

Hi Biran,

Thank you for posting here. Regarding on the issue, I am
finding proper resource to assist you and we will update as soon as posible.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! [url]www.microsoft.com/security(This[/url] posting is provided "AS IS",
with no warranties, and confers no rights.)

[Manohar Kamath [MVP]]

Looks like a Command timeout to me, try increasing your command timeout
property on the connection object and see if this solves the problem.

This could happen because the SQL server is not on the same subnet as your
IIS server. While you can not do much about this (since your hosting
provider controls the infrastructure), you can try to write queries that are
faster (using stored procedures) or optimized to run faster (tweaking the
query clauses, etc.)

--
Manohar Kamath
Editor, .netWire
[url]www.dotnetwire.com[/url]


"Brian Peddle" <brian@nospam.com> wrote in message
news:eg2YGGMcEHA.996@TK2MSFTNGP12.phx.gbl...
I recently moved hosting companies, we went from a Windows 2000 environment
to a Windows 2003 environmennt.

Since the move I have started to get timeout errors about once a day. I
maybe got an error like this once every 4 months before the move.

Microsoft OLE DB Provider for SQL Server (0x80040E31)
Timeout expired

It will occur for any page with a query and it can last anywhere from 30 min
to 3 hours before it corrects itself.

Has anyone every seen this behavior when switching 2000 -> 2003. Any
suggestions for tracking why its happening. I look in the SQL logs and
nothing standouts.

[Yan-Hong Huang[MSFT]]

Hello Brian,

I was reviewing the issue thread. Did you resolve the problem by enlarging
connection timeout value? If the problem is not resolved yet, please feel
free to post here and we will follow up.

A quick code sample should like:
set conn = server.createobject("adodb.connection")
conn.connectionTimeout = x
conn.commandTimeout = x
(x should be in seconds)

Thanks.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C [url]www.microsoft.com/security[/url]
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.