April 11, 2002 at 2:14 pm
Just recently, we've noticed a spate of ODBC Drivers error '80040e31' errors (Timeout Expired) popping up when users access the asp pages.
I've searched online, and there are many instances of this error reported, but there aren't any solutions offered.
Its difficult to recreate the error when testing, and there aren't any definite patterns to follow.
Does anyone have any clues?.. any suggestion?
April 12, 2002 at 5:58 am
Several things can cause this, primary being the query takes to long to return. If the timeout comes immediately then do you have the site to expire immeditely? Any more detail on this you can provide would be helpfull.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 12, 2002 at 8:14 am
We've kinda narrowed the problem. The error most usually (but not always) happen when there are three or four persons accessing the same page at the same time. Other than that, there's not much more to say right now.
April 12, 2002 at 8:42 am
Ok watch the locks being held with Profiler and see if one is holding a lock for long period of time. This should pinpoint the issue since you should be able to reproduce.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 12, 2002 at 8:51 am
OK.. I've started to monitor profiler. What is an average value that would suggest a lock up?
thanks..
April 12, 2002 at 9:10 am
Not sure of a number by I would look at all events under Locks except
Acquired and Released
Starting items for Stored Procedures and TSQL to see what items happen before the timeout.
I think you should see either a deadlock, timeout or cancel lock occurr near when the problem occurrrs.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 12, 2002 at 9:20 am
i'm doing that ... thanks.. really appreciate it
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply