February 25, 2008 at 6:06 am
Hello,
I wonder if someone can perhaps shed some light on possible cause for the mssql server error
message below;
---
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
---
Last week this happened once every day, requiring a mssql reboot making it last another day, and
then all of a sudden the error stopped appearing, but my hosting provider says the site is performing
quite "slowly". But it has been running well for about a week, though at "low speed" as my hosting
provider says. Thing is I had not implemented anything new or daring when this error started
appearing. Can this be patch related, or due to a setting on the IIS/Ms sql server/Windows 2003?
The system is running classic asp against an mssql server, and has been doing so for quite a while
without problems and quite a high usage with lots of queries running.
Regards
/Peter
February 26, 2008 at 9:46 am
hi,
can you try mentioned in the following link:
http://tutorials.aspfaq.com/8000xxxxx-errors/why-do-i-get-80040e31-errors.html
February 27, 2008 at 9:33 am
Joseph, that was a great site in your post. Heres a quick rundown for SomeCoder.
The time event occurs in the ADO client because the server has not responded within the querytimout value set by the client. Perhaps the SQL box was slow running the query because:
1) you have more data now and your queries are inefficient (use query analyzer to check this out)
2) your SQL server was super busy and you've hit the timeout (queries still may need optimization)
3) network access between the SQL server and Web server was slow and the ADO provider throws the timeout event.
4) SQL sever data and indexes are fragmented and you need to run DBCC commands to check this out and rebuild indexes. (Verify maintence jobs are running and that you have appropriate amount of freespace in index to handle the expected activity)
Good luck, please post back your results
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply