Troubleshoot And Resolve Odbc Driver Error 80040e31 Timeout

 

Approved: Fortect

1. Download Fortect and install it on your computer

2. Launch the program and click "Scan"

3. Click "Repair" to fix any issues that are found

Speed up your computer's performance now with this simple download.

In this article, we will identify some possible causes that can cause the odbc driver error 80040e31 to time out and then suggest possible recovery methods that you can try to fix the problem.

 

 

I wrote on an ASP page today that encountered an AJAX call to trigger a number of SQL updates, including an email to a stored procedure. Web publishing started with error:

The error line was a call to some stored procedure. After playing around a bit, I traced your problem back to the ADO ConnectionTimeOut value. The default is 30 seconds.

There are probably three interesting timeout values ​​in the ASP page:

The length of the user’s phone session. In IIS it was 20 to minutes by default

How long does it take to write an article. In IIS, the above default is 90 seconds. Long

how can almost any database call be made. The default is 45 seconds.

The stored procedure lasted> 30 minutes, so an error occurred. I have no doubt solved the problem by increasing the ConnectionTimeOut value to generate a call specifically for the surgical stored procedure, for example:

CmdC gradationSet cmdC = Server.CreateObject (“ADODB.Command”)with cmdC.ActiveConnection means connection.CommandText = “[procedure name]”.CommandType = adCmdStoredProc.CommandTimeout matchesThere is 3000.ExecuteEnd with

The value is specified in seconds, i.e. 3000 seconds = 5 minutes. Can you read more about ConnectionTimeOut here?

There is, of course, another reason why it takes so long to use a single stored procedure as part of an AJAX call. We’ll probably be moving it from work to work at one point or another, but in the meantime, a quick fix was needed.

I am a super backbone developer who currently enjoys maintaining a client-side website that is now using classic ASP using SQL Server 2000.

The code is pretty old and has been updated to a basic new full system as a result of this process, but until then we need to make the sites as smooth as possible.

There are three websites, a commercial front-end, in the UK and just after a back-end in Singapore. Both server modules buy nearly 95% identical codebase, and they each have a database on the same server and are hosted on the same computer.

MY problem is that for the next two or three days,Users have reported errors when trying to log into the Singapore website. Error:

  Microsoft OLE DB Provider for odbc driver error '80040e31'[Microsoft] [ODBC SQL Server Driver] Timed out 

The code in question is a simple and important UPDATE statement that updates a custom session for writing, and this code has worked great for years.

Also, there is no need to make the latest changes to the code, which, according to experts, may affect this. How can I determine the cause of the bottleneck? Event Viewer, SQL error logs, and IIS logs seem to be able to not display errors when certain timeouts occur.

I suspect the error is definitely occurring when this code tries to do an UPDATE, but there was / is a previous process that was causing the server to crash, SQL, but not just the DBA, which I am doing at this point in the question.

  set con2 = server.CreateObject ("ADODB.Connection")con2. connection delay = 1200con2.open "Driver = SQL Server; server = 111.111.111.11; user ID = xx; pwd = xxx; Database = xxx"con2.execute ("REMOVE  FROM table_name, field identifier, where NOT INCLUDED (SELECT field identifier FROM table_name2) ")con2.closedefine con2 = nothing 

When I ran this fix using asp the following error occurred. How to solve this problem ?

Microsoft OLE DB Provider for ODBC Driver error 80040e31

[Microsoft] [ODBC SQL Server Driver] Timed out

 

 

Speed up your computer's performance now with this simple download.