jholton
asked on
Seemingly random 'Timeout expired' '80040e31' error
I have a page on which users submit information.
A few days ago this problem started occurring.
It's seemingly intermittent/random, but is happening frequently enough to be very very annoying.
Here's the error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
/directory/page.asp, line 130
There is no script on the page that should take seconds to run, much less reach the timeout time.
If the page submitting the info gets the error, the page can be refreshed (and data resubmitted) and it will work (sometimes). So, it's not necessarily the data being submitted.
Any ideas?
Thanks.
A few days ago this problem started occurring.
It's seemingly intermittent/random, but is happening frequently enough to be very very annoying.
Here's the error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
/directory/page.asp, line 130
There is no script on the page that should take seconds to run, much less reach the timeout time.
If the page submitting the info gets the error, the page can be refreshed (and data resubmitted) and it will work (sometimes). So, it's not necessarily the data being submitted.
Any ideas?
Thanks.
Do you have SP3 for SQL SERVER instaled?
ASKER
I have:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
You may have a concurency problem, when many users try to insert in the same time rows in one table . You may have to think of locking that table.
Or
When you set the Connection object try to set timeout property to a greater value.
Good luck!
Or
When you set the Connection object try to set timeout property to a greater value.
Good luck!
ASKER
I took the query and ran it in query analyzer.
It's a simple insert and it took 40 seconds to run.
Just tried again and it's fine.
It's like something is clogging it up for a while. At this moment it isn't clogged, but I'm 100% sure it will be before the day is over.
It's a simple insert and it took 40 seconds to run.
Just tried again and it's fine.
It's like something is clogging it up for a while. At this moment it isn't clogged, but I'm 100% sure it will be before the day is over.
40seconds to run for an insert??? Sounds a bit long to me. Did you look at the query plan to see why it's taking so long?
Have you ran Windows Perfmon to see what the diskio looks like? is your log file and database data file on different disks?
Have you ran SQL Profiler to see all the SQL activity that's taking place at the same time?
Paste your insert code...
Have you ran Windows Perfmon to see what the diskio looks like? is your log file and database data file on different disks?
Have you ran SQL Profiler to see all the SQL activity that's taking place at the same time?
Paste your insert code...
ASKER
It did the same thing this morning.
Submit insert from web site. Times out after 30 seconds.
Tried the insert from Query Analyzer. It took 40 seconds, but worked.
Now inserts work as fast as they should from the site and QA.
The query plan looks fine now. Unfortunately, I didn't have it running when the query took 40 seconds.
Parden my ignorance, but I don't know how to use the Perfmon to evaluate the disk IO.
Log file and database file are on same disk.
Thanks.
Submit insert from web site. Times out after 30 seconds.
Tried the insert from Query Analyzer. It took 40 seconds, but worked.
Now inserts work as fast as they should from the site and QA.
The query plan looks fine now. Unfortunately, I didn't have it running when the query took 40 seconds.
Parden my ignorance, but I don't know how to use the Perfmon to evaluate the disk IO.
Log file and database file are on same disk.
Thanks.
Would you also right click on the database in Enterprise Manager and choose properties. Look at the options tab. Do you have the "Auto Close" option selected?
Update speed can be improved if you move your log file onto a different disk from the data file (and from a recoverability standpoint, it should be any way).
Windows Performance Monitor (Start/Run, PERFMON). You can add a counter for Performance Object PhysicalDisk and look at Avg Disk Write Queue Length and the Avg Disk Read Queue Lengths (for starters).
Update speed can be improved if you move your log file onto a different disk from the data file (and from a recoverability standpoint, it should be any way).
Windows Performance Monitor (Start/Run, PERFMON). You can add a counter for Performance Object PhysicalDisk and look at Avg Disk Write Queue Length and the Avg Disk Read Queue Lengths (for starters).
ASKER
I've gotten busy today, but I'll try your suggestions when I get the time to.
Is there a way to increase the script timeout value for SQL Server?
Thanks.
Is there a way to increase the script timeout value for SQL Server?
Thanks.
There are several different timeouts (not sure what your code looks like):
server.scripttimeout=0 ' don't timeout at all
connection.timeout=600 'command will timeout after 6minutes
server.scripttimeout=0 ' don't timeout at all
connection.timeout=600 'command will timeout after 6minutes
ASKER
The problem was the log file for the database wasn't committing properly after backups and had grown to 13GB.
We fixe that and the problem went away.
Thanks.
We fixe that and the problem went away.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.