The database connection was ok without specify any pooling parameter, however, after I decide to put pooling parameter to the connection string. I frequently expierence "Time out expired" exception.
Here is the connection string: "Pooling = True; Min Pool Size = 5; Max Pool Size = 100;Server = servername; AttachDbFilename = database_file; Integrated Security = True;"
As you see, it is not much different from default value.
I was thinking may be I should give a "Time out" value to the connection, will this help?
I'm getting the following error in my v1.1 page: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Not sure why, since I'm trying to close the connection right when I'm done, and I've got the timeout set to "30" Select Case DBselected Case "DB8" Try Dim sCon1 As New SqlConnection sCon1.ConnectionString = ConfigurationSettings.AppSettings("db8") Session("DBDDL") = sCon1.ConnectionString.ToString() sCon1.Open() Dim cmd As New SqlCommand("[usp_Security]", sCon1) cmd.CommandType = System.Data.CommandType.StoredProcedure cmd.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IDNumber", System.Data.SqlDbType.NVarChar, 50)) cmd.Parameters("@IDNumber").Value = Session("User") Dim DR As SqlDataReader = cmd.ExecuteReader If DR.HasRows = False Then btnSwitchboard1.Enabled = False lblnotice.Visible = True lblnotice.Text = "The IDNumber, " & strIDNumber & ", doesn't exist in the database for access permission!" Else btnSwitchboard1.Enabled = True lblnotice.Visible = False End If DR.Close() DR = Nothing Catch ex As Exception lblStatus.Text = "Error building IDNumber: " & ex.Message Finally sCon1.Close() End Try Case "DB1" Try Dim sCon1 As New SqlConnection sCon1.ConnectionString = ConfigurationSettings.AppSettings("db1") Session("DBDDL") = sCon1.ConnectionString.ToString() sCon1.Open() Dim cmd As New SqlCommand("[usp_Security]", sCon1) cmd.CommandType = System.Data.CommandType.StoredProcedure cmd.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IDNumber", System.Data.SqlDbType.NVarChar, 50)) cmd.Parameters("@IDNumber").Value = Session("User") Dim DR As SqlDataReader = cmd.ExecuteReader If DR.HasRows = False Then btnSwitchboard1.Enabled = False lblnotice.Visible = True lblnotice.Text = "The IDNumber, " & strIDNumber & ", doesn't exist in the database for access permission!" Else btnSwitchboard1.Enabled = True lblnotice.Visible = False End If DR.Close() DR = Nothing Catch ex As Exception lblStatus.Text = "Error building IDNumber: " & ex.Message Finally sCon1.Close() End Try Case "DB2" Try Dim sCon1 As New SqlConnection sCon1.ConnectionString = ConfigurationSettings.AppSettings("db2") Session("DBDDL") = sCon1.ConnectionString.ToString() sCon1.Open() Dim cmd As New SqlCommand("[usp_Security]", sCon1) cmd.CommandType = System.Data.CommandType.StoredProcedure cmd.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IDNumber", System.Data.SqlDbType.NVarChar, 50)) cmd.Parameters("@IDNumber").Value = Session("User") Dim DR As SqlDataReader = cmd.ExecuteReader If DR.HasRows = False Then btnSwitchboard1.Enabled = False lblnotice.Visible = True lblnotice.Text = "The IDNumber, " & strIDNumber & ", doesn't exist in the database for access permission!" Else btnSwitchboard1.Enabled = True lblnotice.Visible = False End If DR.Close() DR = Nothing Catch ex As Exception lblStatus.Text = "Error building IDNumber: " & ex.Message Finally sCon1.Close() End Try Case "DB3" Try Dim sCon1 As New SqlConnection sCon1.ConnectionString = ConfigurationSettings.AppSettings("db3") Session("DBDDL") = sCon1.ConnectionString.ToString() sCon1.Open() Dim cmd As New SqlCommand("[usp_Security]", sCon1) cmd.CommandType = System.Data.CommandType.StoredProcedure cmd.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IDNumber", System.Data.SqlDbType.NVarChar, 50)) cmd.Parameters("@IDNumber").Value = Session("User") Dim DR As SqlDataReader = cmd.ExecuteReader If DR.HasRows = False Then btnSwitchboard1.Enabled = False lblnotice.Visible = True lblnotice.Text = "The IDNumber, " & strIDNumber & ", doesn't exist in the database for access permission!" Else btnSwitchboard1.Enabled = True lblnotice.Visible = False End If DR.Close() DR = Nothing Catch ex As Exception lblStatus.Text = "Error building IDNumber: " & ex.Message Finally sCon1.Close() End Try Case "DB4" Try Dim sCon1 As New SqlConnection sCon1.ConnectionString = ConfigurationSettings.AppSettings("db4") Session("DBDDL") = sCon1.ConnectionString.ToString() sCon1.Open() Dim cmd As New SqlCommand("[usp_Security]", sCon1) cmd.CommandType = System.Data.CommandType.StoredProcedure cmd.Parameters.Add(New System.Data.SqlClient.SqlParameter("@IDNumber", System.Data.SqlDbType.NVarChar, 50)) cmd.Parameters("@IDNumber").Value = Session("User") Dim DR As SqlDataReader = cmd.ExecuteReader If DR.HasRows = False Then btnSwitchboard1.Enabled = False lblnotice.Visible = True lblnotice.Text = "The IDNumber, " & strIDNumber & ", doesn't exist in the database for access permission!" Else btnSwitchboard1.Enabled = True lblnotice.Visible = False End If DR.Close() DR = Nothing Catch ex As Exception lblStatus.Text = "Error building IDNumber: " & ex.Message Finally sCon1.Close() End Try
Hi, I have a problem in my .net application. I am executing a stored procedure from my .net application. The scope of this stored procedure is, 1.It should filter the records using several conditions(say it is Customer) 2.Using the filtered records, again some details are fetched(say it is transaction details) 3.For each and every transaction , Some of the details has to be updated in more than three tables, meanwhile the data to be updated is to be calculated (like tax amount, commision amount)which in turn calls two more stored procedures.
my problem is .. if there are few records like 1000 or 2000, it is working fine... but if it exceeds like say 6000 records, i am getting Time out expired error in my application . If i catch the stored procedure exectution statement in sql profiler and execute it in Sql Query analizer , the stored procedure is executing properly but it takes nearly 6 minutes. How can i solve this problem. Please suggest me if i can work with any of the following options. 1)go for web services 2)go for windows services 3)optimize the stored procedure
If any one know some better answer to solve my problem..please post it.
We have a C++ program that connects to a remote SQL Server database. Recently the system we pull data from upgraded to SQL Server 2005 and my program can no longer connect to the database. We're getting TimeOut expired errors (not login timeout expired) within 15 - 20 seconds after attempting to open the connection. I have confirmed with this other system that my id does not show up in any logs on their end. Here is some background: Nothing has changed on my end. We have another system that my team supports that is able to connect, and they have changed nothing. They're using a different connection method. We're using oledb and they use odbc and a different provider. I confirmed with the SQL Server team that this id made a connection.
Connect String:
Provider=SQLOLEDB.1;;User ID=XXX;Password=xxxx;Data Source=serverdb instance;Initial Catalog=xxxx; From what i've read, etc this connect string should work still
Here is an example of the code and context of this connect string
'Set connection object pTEST_HR(pConnect.CreateInstance(__uuidof(Connection))); pConnect->ConnectionString = OurConnectString; pConnect->Open("","","",adConnectUnspecified); 'Create and open recordset TESTHR(pRstEmployee.CreateInstance(__uuidof(Recordset))); pRstEmployee->Open("Employee", This is the point at which we get a timeout. _variant_t((IDispatch *)pConnection,true), adOpenKeyset, adLockOptimistic, adCmdTable);
Server Info: I have succesfully pinged the server The client is not in the same domain as the db server
Error: Appl: A database error has occured -> Error Code = 80040e31 Code meaning = IDispatch error #3121 Source = Microsoft OLE DB Provider for SQL Server Description = Timeout expired
Other info: Not sure about my client database provider. This is coded in Visual C++ 6.
I'm not knowledgeable on SQL Server configuration, etc.
Things i've tried so far Change provider from SQLOLEDB.1 to SQLOLEDB Change provider to SQLNCLI Had SQL server query time out set to never time out. The remote login timeout changed to 600 seconds from 30 seconds. However we are getting a timeout in only a few seconds, so i find that interesting.
Can anyone see a reason that the application keeps timing out, it was work fine a couple of days ago. private DataTable Search6HostPlaces(string host) { DataTable dt; host = lblHostname.Text; SqlConnection cn = new SqlConnection(ConfigurationManager.AppSettings["ConnectionString"]); SqlCommand cmd = new SqlCommand("matchHost", cn); cmd.CommandType = CommandType.StoredProcedure; cmd.Parameters.AddWithValue("@pHost", host); SqlDataAdapter sda = new SqlDataAdapter(); sda.SelectCommand = cmd; DataSet ds = new DataSet(); cn.Open(); <--------------------------------------------------------Timeout when is gets here sda.Fill(ds, "HostName"); dt = ds.Tables["HostName"]; cn.Close(); //dt.Rows.Count.ToString(); return dt; } public void CountRecords() { DataTable dt = Search6HostPlaces("host"); lblTest.Text = dt.Rows.Count.ToString(); }
when developer to retreive the data through ssms it displays like this
Error source:- .Net Sql Client Data Provider Error message :- Time out expired. The time out period elapsed prior to completion of theoperation or the server not responding.
i checked in ssms tools -->options-->query execution is 0. Last week for all users it display the same above .wht may be the problem. why it happens?
pls do the needfull.. thanks in advance regards manoj
When I try to add an item in App_Data ,in ASP .NET it says "Time out expired.Timeout period elapsed prior to completion of the operator or the server is not responding."
Hi Actually i have developed an Web application(intranet) and I put it on IIS which will be using it more than 5 persons at a time. In that application there is a page which will interact more to Database(SQL server 2005). Problem is when persons working on that page some times it throws an error message like "Timeout expired. the timeout period elapsed prior to completion of the operation or the server is not responding". I think it is because of SQL server but i don't find exactly. Plz tell me what is problem and how to solve it.
My application works with the Connection pooling ODBC. Everything works well, when it data base this down the SQLConnect function finishes steeply my application.
We are running SQL2K5 and have a Web server with a family of sites all sharing an identical connection string to enable ADO connection pooling between them. Today for about 20 minutes we had several (all?) connections from one site that uses a specific DB get a connection reuse error which showed in out SQL logs:
DESCRIPTION: The client was unable to reuse a session with SPID #, which had been reset for conection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
We also have SQL Server slowdown and log in problems from other applications that seemed a symptom of this, or some third unknown cause. Note, the # means the run-time spid number was inserted. The misspelling "conection" comes right out of sys.messages (it is not our custom error):
select top 10 * from sys.messages where message_id = 18056
The immediately preceeding error in the SQL Log was always: Message Error: 18056, Severity: 20, State: 29.
Where Severity and State vary, but "Error: 18056" is consistent, although I can find no documentation on "Error: 18056" through Google or MSDN.
Also, the "The client was unable to reuse a session ..." error seems not to be referred to anywhere.
In our IIS logs, the matching entries are of the form:
[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.
and
Invalid connection string attribute
My questions: Does anyone have experience with this error? We have real good history with ADO connection pooling, but can a "bad" connection be pooled, and if so can it be "flushed" or the pool "drained"?
[Posting this in the security forum because in this forum I found a related post.]
I have a problem with SQL Server 2005 and application roles and pooling. I needed to use application roles and I needed to use pooling at the same time for an application. I am using sp_setapprole and sp_unsetapprole. In order to ensure that the application role is always set and unset by the application, I actually developed a custom Data Provider based on the SqlClient Data Provider. I have a custom Connection and Command class that wrap the SqlClient versions. Upon opening my custom Connection class, I execute the sp_setapprole stored procedure. Upon closing or disposing the connection, I call sp_unsetapprole.
This works fine in 99% of my tests. However, I have three or four methods (always the same ones, but one only fails ever so often) that fail, but only under the following circumstances:
Pooling is turned on (but pool size doesn't matter)
I am using my custom Data Provider (using System.Data.SqlClient does not cause this issue... but I am also not using approles then)
When other tests have run in the same test run. I.e. when I run the failing methods by themselves in a test run, there is no problem. So it seems to me that the problem is related to using application roles with pooling turned on. For scalability reasons, we cannot turn pooling off. When the methods fail, I see the following two (2) entries in the SQL Log:
Error: 18059, Severity: 20, State 1.
The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See "Impersonation Overview" in Books Online. I understand the error message somewhat. However, I am not sure why the "reset" of the connection occurs. My code does not call reset anywhere, so it must be something that happens in the background.
I am reviewing code to see if there is possibly a situation where the sp_unsetapprole procedure does not get called or does not get called successfully, but there is a lot of code (in many custom components).
I would like to know if anyone has a suggestion on how to solve this problem, or, find the code that may be causing the problem.
Hi everybody, I do custom log shipping over network like
step 1 backup log to C:.. step 2 zip log file c:... zip step 3 copy zip to \sm01 estorelogs... step 4 unzip file step 5 restore log with stand by
Few times a month it fails with
Error = -2147467259 (80004005) Error string: Timeout expired Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 0 (0) Error string: Timeout expired Error source: Microsoft OLE DB Provider for SQL Server
We have several large government web sites that we help look after. We recently migrated one of them from SQL Server 2000 to 2005 and are having a problem with our nightly email job in that if it runs for more than an hour then after exactly 1 hour the email job gets a "Timeout expired" message back from SQL Server.
Our batch jobs do run on a different server and connect remotely to our SQL Server DB. I did change the connections - remote query timeout and increased it 10 fold, but this didn't make any difference. Is there any other parameter that may be causing the Timeout expired error after exactly 1 hour?
I have an Update stored procedure that is used to update four tables at the same time. The issue is that it works perfect when i run the application in local server,but when i upload the application on to the server that is located in U.S, it gives an error "System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. " I think the sqlCommand is timing out and the value is not returned. Is there a workaround to this issue? What could be the reason for this? Any ideas.. Please help..
Hi: Just purchased a web application, sometime it will cause the timeout error, that will cause the web page can't be opened, and popup an error page."Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." The function is below:public static ProfileAnswer[] FetchNonApproved() { using (SqlConnection conn = Config.DB.Open()) { SqlDataReader reader = SqlHelper.ExecuteReader(conn,"FetchNonApprovedAnswers"); //this is the line where the timeout error occurs.
List lAnswers = new List();
while (reader.Read()) { //do something here lAnswers.Add(answer); }
return lAnswers.ToArray(); } }
Is there anyway to jump out of the error if the timeout occurs, abort the further action, and back to current page. (what is the problem with the code?) Thanks a lot. Jt
I am getting this error sometimes what can I do for this
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
My application always face timeout expired error (as following) whenever i first run the application. But it can run well for second time. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Is there any suggestion or advice for me about this problem? Thank You.
I am getting problem from one of my client that is.. connection Failed: SQLstate: 'HYT00' Sql Server Error: 0 [Microsoft] [ODBC Sql Server Driver]TimeOut expired. How to solve it please solve....
Hello:I have an application (using ADO 2.7 - written in VB) that access a SQLServer 2000 Database.Every once in a while, the program hangs when I am accessing the DB, andsometimes I get a timeout expired error. The wierd thing is, when it hangs,if you try the function again - it goes throught every timeFor example, If I call a function that retrieves a password from a table inthe DB, it will hang (sometimes it hangs for a few seconds and then goesthrought, sometimes it will timeout and gives me the timeout expired error).If I then call the same function immediately after, there will be no delay.I am stumped on this, any help would be appreciated. I have tried shrinkingthe DB and Backing it up to no avail.Regards,Ryan Kennedy
I am getting error Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. StackTrace> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) at Galileo.Modules.Data.DBDeclare.RunProcedure(String sp, IDataParameter[] parameters) at GalileoModules.Data.PrivateAccomodation.Search3.Query(String[] values
I am using a VB script active task object in a DTS package to connect to one of my databases using an OLE DB connection. I send an SQL string executing stored procedures, and depending on the size of the procedures I get a "Timeout Expired" error on execution of the DTS package. I have trimmed and tuned the stored procedures to be much smaller and faster, but still haven't beaten the timeout. How do i avoid, switch off, or lengthen the timeout period?
Thanks, Joshua
PS, alternately, how might I modify the parameters of and execute DTS packages from stored procedures?
i am using sql server 2000. and have a DTS with script in it. now the script if failing saying timeout expired. The script has db connection and calls stored procedure to fetch data. The records are around 63K but its failing due to timeout expired.
is there a way to increase the timeout in script. i dont want to do any changes to sql server settings.
When i am connecting Report Manager report through our ASP.NET 2.0 application using Report Viewer control frequently we get message ASP.Net Session expired .
How can we avoid this error.While i directly opens Reports through the Report Manager reports are opening without any problem.
My .Net application Code. ReportViewer1.ServerReport.ReportServerUrl = new Uri("http://SERVER/reportserver"); ReportViewer1.ServerReport.ReportPath = @"/myreport/reportname";
I was having some errors from the webpage accessing the OLlinks table in the database. Error executing non query: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at admin_admOLEditLinks.selectData(String strID) in e:wwwroothomeadminadmOLEditLinks.aspx.cs:line 101DateTime:5/23/2007 1:14:10 PMSource:http://www.myDomain.comiAdmin/admOLEditLinks.aspx?ID=3ErrorMessage:Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. I kept getting the above error so then I try to access the table directly inside of MS SQL Server Management Studio and then I recieved the following error: SQL Execution Error. Executed SQL statement: SELECT lnkID, linkFromID, linkToID FROM OLlinks Error Source: .Net SqlClient Data Provider Error Message: Timeout expired. The timeout period elapsed prior to completion of the opration or the server is not responding.
Open any other table works fine except this table only. Any help is much appreciated.
I get this timeout error from the member login page. It does not happen always. Sometimes when I enter the email and password and try to login, it will take forever and then it throws a timeout error. "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
I went into our server, started the sql profiler and tried to run the login sproc manually from the query analyzer. It took 46 secs to finish running the query. I checked the profiler, there was nothing much going on, I don't think there is any resource bottleneck.
I went back to the website and I tried to login, it worked fine. I checked the query analyzer again, this time it took 0 secs (or fraction of a sec?) to execute the sproc.
It looks like it takes a long time to run the sproc the "first" time, from then on it only takes less than a sec to execute the sproc. How do I solve this problem?
The users table has only 50,000 users. The sproc is only a couple of lines. The user table is indexed on userid and email.
------------------------------ CREATE PROCEDURE [dbo].[proc_userverifylogin] @email varchar(100), @pass varchar(50) AS
IF EXISTS (SELECT * FROM users WHERE email = @email AND pass = @pass) BEGIN UPDATE users SET lastlogin = GETDATE() WHERE email = @email SELECT userid, fname, state FROM users WHERE email = @email END ------------------------------
Hi, I'm running an MSAccess2000 Project and while I'm running the program, it keeps giving me a timeout expire error, with a locking error number. It seems that if I truncate the database the I could just continue processing. Is there any way to truncate the log file through code VB6? Or any suggestion regarding this problem? Thanks
Very common error but wired scenario. Every client machine get this error in morning. VB application works fine until evening but when everyone goes home after shut down the machine and they come back again in morning and try to run the application they get this error. Application runs fine, It can access data, pull data, view data but It can not write any data. (Other words can not enter any data).
Application again starts working fine after I copy database on different SQL server. For temporary solution I swap database from one SQL Server to other one day and back to original SQL server next day. Every morning it takes about 2 hours to copy database. I’m doing this from last few days as working solution. FYI, I have 2 different VB application, each has their own database. One working fine and other started giving me problem, the one I described above.
Few thing I want to let you know:
Recently I changed the SQL server. After I changed I started having this problem. But other application working fine. So I don’t think that could be a problem. (Both application basically same in terms of development and tools they use. VB and SQL Server, ODBC connection, Crystal Reports).
In old SQL server both database had daily backup on third party backup built on different server using Client Network Backup. After I changed the SQL server I never modify backup setting. So after I moved SQL server , every night backup was trying to connect to old SQL server and but It couldn’t take the backup cause I changed the machine. Again if that’s the problem both application should not work but one working fine other is giving me problem.
One more thing I want to mention here is I started having this problem when I left the SQL server copying database overnight. Means, I started copying database and I left the machine ON when I came in the morning copying database was done and I just click on the OK and close the window. Basically It has finished copying database in around 2 hours after I started and I close the window when I came back next morning.
That’s the few things I’m thinking about but I don’t know what kind of database setting this might have changed and how to reset again. Any help will appreciated.
Dose any one know how to combine .mdf (Primary data file) and .ndf (secondary data file) ???
I am getting this error when I try to back up the larger DB's on myserver. The smaller ones back up ok. Is there a parameter I can changeto increase this timeout? I have gone into ODBC, Query Analyzer, andSQL server properties and played around with some settings, but nothingseems to work.Any help is appreciated!Phil
sql server 2000 8.00.194Microsoft Windows 2000 Service Pack 2I looked into my sqlserver agent log and found the followingODBC Error 0 Timeout expired[SQLSTATE HYT00]logon to server local '( failed)' (Job manager)I have no idea what that means but it did keep out users for a minute or more.The threads found on this forum almost all point to reccuring situationsmine is a sporadic one time issue.Is it Ok to conclude it is a network error as I did?TIAVince
we are working on a web application created in ASP & SQL 2000 environment. In the code , we have a single connectionstring to connect database. The application was running fine for the past 3 years, but all of a sudden we are getting "timeout expired" error only in someparts of the application but not on all database access. The code which raises this error is a bit large which need to look into table of 8k recs with more conditions. The same sql query took 1:01 minutes to execute in query qnqlyser. I changes the script timeout to 900secs, I herd we need to upgrade MDAC or we need to change connection timeout or we need to cahnge the code.
we cannot change the query, it is the most possible way we could get that.
