Hi I have an ASP page that runs a stored procedure to pull data back from the SQL 2005 server. The query runs fine in SQL Query Analyser and takes approx 45 seconds. At exactly 30 seconds i get the 80040e31 - Timeout Expired. I have set the CommandTimeout value at 60000 'conn.commandtimeout=60000' Still the connection times-out after 30 seconds. The query does work as it has it works occasionally but not very often. The problem appears to be that something is ending the communication. Hi Dan Can you expand what you mean a little? I was getting this error starting on Friday. Code: Microsoft OLE DB Provider for ODBC Drivers error '80030e31' [Microsoft][ODBC SQL Server. Microsoft][ODBC SQL Server Driver]Timeout Expired Feb 1, 1999. Hi all, I inherited some really twisted asp pages from another developer that crank for a long time. Codul bunelor maniere astazi. Here is my connection string, I tried to add in command.CommandTimeout = 60000 But the object 'command' doesn't exist _________________________________________________________________________ MM_dataconn_STRING = 'Provider=SQLOLEDB;' & _ 'Data Source=111.222.333.444;' & _ 'Initial Catalog=databasename;' & _ 'Network=DBMSSOCN;' & _ 'User Id=username;' & _ 'Password=password' set conn = CreateObject('ADODB.Connection') conn.connectiontimeout=30000 conn.CommandTimeout=60000 command.CommandTimeout = 60000. I am running a query which pulls back about 200,000 records. When I run this in ISQL (SQL Server 6.5), it runs in almost 2 minutes. When I put it in a store procedure and run it off my ASP application, I get this error [Microsoft][ODBC SQL Server Driver]Timeout Expired We've tried many things including: 1) Increased connection and command time outs in Global ASA 2) Have the ODBC driver log long Quires to a file 3) Changed Query Time out in Enterprise Manager(360 seconds) Go to tools --> Preferences/configure -->Connection Tab 4) Changed Maximum allowed open database from 20 to 200 5) Changed resource timeout to 360 seconds from 5 seconds 6) Changed remote query timeout to 0, allowing infinite wait. What else can we try??? Thanks for taking the time to read this Joyce. ![]() Are you using named pipes? Thomson speedtouch 580 usb driver. Microsoft recommends TCPIP Sockets for web applications. Something to do with the queuing of network requests. ------------ Joyce at 8/19/99 2:44:38 PM I am running a query which pulls back about 200,000 records. When I run this in ISQL (SQL Server 6.5), it runs in almost 2 minutes. When I put it in a store procedure and run it off my ASP application, I get this error [Microsoft][ODBC SQL Server Driver]Timeout Expired We've tried many things including: 1) Increased connection and command time outs in Global ASA 2) Have the ODBC driver log long Quires to a file 3) Changed Query Time out in Enterprise Manager(360 seconds) Go to tools --> Preferences/configure -->Connection Tab 4) Changed Maximum allowed open database from 20 to 200 5) Changed resource timeout to 360 seconds from 5 seconds 6) Changed remote query timeout to 0, allowing infinite wait. What else can we try??? Thanks for taking the time to read this Joyce. I know this is going to sound.weak, but try upgrading to MDAC 2.1 on the WEB/IIS server. After doing that, you might want to try creating a single DSN on the Web server to point to your database and configure it to use TCP/IP Sockets only.even though you are not using ODBC to connect to your database, I've seen these things fix issues like this. ------------ Cindy Gross at 8/21/99 9:55:57 AM Are you using named pipes? ![]() Microsoft recommends TCPIP Sockets for web applications. Something to do with the queuing of network requests. ------------ Joyce at 8/19/99 2:44:38 PM I am running a query which pulls back about 200,000 records. When I run this in ISQL (SQL Server 6.5), it runs in almost 2 minutes. Ludwig drum badge serial numbers. When I put it in a store procedure and run it off my ASP application, I get this error [Microsoft][ODBC SQL Server Driver]Timeout Expired We've tried many things including: 1) Increased connection and command time outs in Global ASA 2) Have the ODBC driver log long Quires to a file 3) Changed Query Time out in Enterprise Manager(360 seconds) Go to tools --> Preferences/configure -->Connection Tab 4) Changed Maximum allowed open database from 20 to 200 5) Changed resource timeout to 360 seconds from 5 seconds 6) Changed remote query timeout to 0, allowing infinite wait. What else can we try??? Thanks for taking the time to read this Joyce.
0 Comments
Leave a Reply. |