OLEDB Timeout expired problem 2

[somecoder]

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

 

[jdemmi]

What version of MDAC do you have installed? Have you checked or upgraded to the latest?

-- Jason
"It's Just Ones and Zeros

 

[SQLSister]

Also consider udating statistics and reindexing

"NOTHING is more important in a database than integrity." ESquared

 

[cmmrfrds]

I believe the default timeout on the ADO connection is 30 seconds. You can modify to suit your needs. The property name is CommandTimeOut.

 

[somecoder]

Modifying the default timeout would not help. Because this error would persist even with the tiniest sql insert/update queries being executed, until the point that I reboot the mssql server. Note, that normal SELECT queries would work. They would be very slow, but working.

Was there an MDAC patch released last sunday (feb 17th) that patches up this kind of error?

What could have caused the error to appear all of a sudden (it started feb 13th)?

Also, I forgot to mention. The timeout error appeared after the mssql had used up basically all memory, which was then freed on reboot. May be a very important factor to consider?

Would reindexing really cure this sort of "memory-leak" like problem?

Regards

/Peter

 

[jdemmi]

somecoder...you asked questions, we've provided suggestions and asked other questions in an attempt to assist you.

if you do not value our input then just ingore us.

in the future you may wish to include in your posts EVERYTHING you've already tried in addition to things you DON'T THINK would fix the problem or things that you're not willing to consider.

And btw...no there was no MDAC patch released last week that will fix this problem. But just because this problem just started to occur DOES NOT mean that you're not experiencing a bug fixed in a PREVIOUS PATCH

Many claim this error can resolved by applying MDAC updates.

http://tutorials.aspfaq.com/8000xxxxx-errors/why-do-i-get-80040e31-errors.html

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2339314&SiteID=1

http://www.dbforums.com/archive/index.php/t-868889.html

-- Jason
"It's Just Ones and Zeros

 

[somecoder]

Apologies, I am of course very thankful for your input. That did not come across well though. Thanks a bunch for the links referring to similar cases! This helps a lot. I did not mean to nullify your suggestions, I was merely trying to bounce my thoughts to your suggestions back to engage other suggestions and thoughts.

/Peter