Occassionaly I get the following error, always when storing a record: Microsoft OLE DB Provider for ODBC Drivers error '80040e31' [Microsoft][ODBC SQL Server Driver]Timeout expired Googling around I see ways of setting the expiry time but why is the database not responding in the first place? It seems to me this has only started to occur with MS Server 2003, I don't recall it happening in MS Server 2000.

It does seem to occur if the page has been idle for a while but I couldn't swear to that. This is not a very busy server.

We are not dealing with a lot of records. I have these settings in my asp pages header: Server.ScriptTimeout = 50000 session.timeout = 1000 So it can't be my script or session timing out, the script is in seconds, the session minutes, I'm talking about less than an hour that the page has been idle. Thanks for any help. Simon Wigzell wrote: Occassionaly I get the following error, always when storing a record: Microsoft OLE DB Provider for ODBC Drivers error '80040e31' [Microsoft][ODBC SQL Server Driver]Timeout expired Nothing to do with your problem, but why are you using ODBC? Judas San Pedro Serial Killer Wiki.

>Googling around I see ways of setting the expiry time but why is the database not responding in the first place? Hard to say without knowing what you are trying to execute.

ODBC Drivers error '80040e31' - [Microsoft][ODBC SQL Server Driver]Timeout expired, Chris, 4/17/01 7:32 AM. I have set up a SQL Server connection to my database and everything pretty much works fine. I have one page that runs a longer query that sometimes goes beyond the default timeout period (60 seconds,. Nov 28, 2013. This object has a CommandTimeout property expected to have a 30 seconds value. I tried to setup the value to 0, which means an unlimited timeout and I had no more the 80040e31 error. Then I tried a 30 value, and again, it worked. For some reasons, it looks like the defalut value for the CommandTimeout. Nov 13, 2010. I was working on an ASP page today that included an AJAX call off to trigger various SQL updates, amongst which was a call to a stored procedure. The page started to error with: Microsoft OLE DB Provider for SQL Server error '80040e31' Timeout expired. The error line was the call to the stored procedure. Microsoft OLE DB Provider for SQL Server error '80040e31' Timeout expired. ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver]Timeout expired.

It seems to me this has only started to occur with MS Server 2003, I don't recall it happening in MS Server 2000. It does seem to occur if the page has been idle for a while but I couldn't swear to that. This is not a very busy server. We are not dealing with a lot of records. I have these settings in my asp pages header: Server.ScriptTimeout = 50000 session.timeout = 1000 These are totally irrelevant. Look at your error message. See where it's coming from?

Is it saying anything at all about a script timeout or a session expiring?;-) This is an ADO timeout. Specifically a CommandTimeout. The ADO Connection object has a CommandTimeout property. If you are using a Command object, it also has that property. This should help explain things: -- Microsoft MVP - ASP/ASP.NET Please reply to the newsgroup. This email account is my spam trap so I don't check it very often. If you must reply off-line, then remove the 'NO SPAM'.

Dictionnaire Pour Router Keygen. Please start any new threads on our new site. We've got lots of great SQL Server experts to answer whatever question you can come up with. Adventureworks2012 Download on this page. Our new are live!

Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Username: Password: Save Password SQL Server Error '80040e31' (timeout) Author Topic Starting Member Australia 5 Posts Posted -: 20:23:18 I am have problems altering a SQL Server table from an ASP application. The SQL Statement is: ALTER TABLE Policy ADD thisisatest nvarchar(255); And the error I am receiving is: Microsoft OLE DB Provider for SQL Server error '80040e31' Timeout expired /mhia/addfields.asp, line 89 I have tried passing the statement in Query Analyser and the syntax is correct, however the execution time is now up to 00:23:40 and still counting. So there is obviousley a problem here. When running the statement over the network or locally on the server I get the same error.