I am getting this error when I try to back up the larger DB's on my
server. The smaller ones back up ok. Is there a parameter I can change
to increase this timeout? I have gone into ODBC, Query Analyzer, and
SQL server properties and played around with some settings, but nothing
seems 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
View 1 Replies View RelatedHi,
I am running a stored procedure that collects some records from two tables do some calculations with those records and insert those calculation result in a temp. table. I am calling this stored procedure in my aspx page and then later select all the records from temp table and show it in a table.
When I run this application on browser it give me Timeout expired error but whn I execute the stored procedure it runs properly but takes around 3:10 mins to execute in query analyzer. I did some google work and based on that I specified CommandTimeout = 300 for SP and Connection timeout=400 in web.config. But still it didnt worked. Sometimes it runs properly but sometimes its not.
Where I am doing mistake? and Wht should i do to resolve this? Plz. help.
Thanks in adv.
Regards,
Yogita
Guys,
I am trying to attach a database object to the App_Data directory I got thie error
Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This is what I did. I right click the App_Data folder and click Add New Item. Then I click the SQL Database. This is where I got the error.
What should I do? Please help
Hi,I
get this error from our web application every once in a while. " Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding". I email
myself when an error occurs, and once every 2-3 days I get this timeout
error emails, like 5-10 emails in a span of few minutes. Then it goes
away. I have set the command timeout for 60 secs.
It
doesn't happen from the same stored procedure, actually I have seen it
timeout from really simple 1 or 2 line stored procedures, which shouldn't normally take 1 sec. Its like
sql server just shuts down for few minutes. We have some
backups and maintenance jobs scheduled, but they run only after
midnight. I have checked the
application event viewer, there are no warnings or
error messages for MSSQLSERVER. Can
any one tell me how to check whats going on during that short timespan
when timeout error occurs, and what causes it? I don't want to run sql
profiler continuously for 2-3 days, I am afraid it will slow down the
server more. Thanks.
Hi,
I have SQL Server 2000 with SP4. When we take backup from Enterprise manager its fails with error "timeout expired". But when we take backup from query analyzer it works.
It seems that through enterprise manager 30 sec is the non configurable timeout parameter set. Checked sysprocesses table during backup but there was no blocking during that time at least for that spid.
Is there a way to find out which process is blocking the database backup? Also, what are the possible scenarios where database backup can be blocked.
Thanks,
Ramesh
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
Hi;
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.
thank you...
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.
Can anyone please help me... I'm getting the following error and the database
I'm dealing with only has about 10 records in it.....
-----Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
Any help would be greatly appreciated. I'm running SQL 7.0
Thank you,
T. Teal
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
View 1 Replies View RelatedI 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
If I don't cache this page, would that help?
Any other suggestions?
Hello,
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.
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
Any idea ,what might cause it ?
Thank you
Alex
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?
Thanks !
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.
Hi,
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
------------------------------
Thanks.
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
View 3 Replies View RelatedVery 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) ???
Hi everyone
I have installed SQL server on my server machine. using localsystem and mixmode option.
It is working fine.
I installed sql server with connectivity tools only option on my client computer.
now, When i try to connect to server using data source from control panel --> Administrative tools --> Data source(ODBC).
but I cant connect.It gives me error as below.
Connection Failed:
SQLState:'HYT00'
Sql Server Error:0
[Microsoft][ODBC SQL Server Driver] Timeout Expired.
I uninstalled sql server from my client and server computer. and installed again.
I tried to ping from client computer to server computer it is working.
even i tried telnet sqlservername 1433
this one is also ok.
But same error facing
Please help me out.
Regards,
ASIF
Hi All,
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.
Can somebody help me with the possible solution.
Thanks & Regards,
Sai. K.K
Hello All,
My application is dependent on two databases one is on sql 2005 machine and other is on sql 2000 machine. A linked server is establish between these two using sql account which has appropriate rights on both server's databases.
application works fine but after some time it crashes and if i see error from sql profiler i get the error
OLE DB provider "SQLNCLI" for linked server "sql2000machine" returned message "Login timeout expired".
Few days back applciation was working absolutly fine, but i was trying to make linked sever through windows account, i dnt know wat has i changed during achiveing that setup that now application (linked server) is not working even with sql account.
please help its urgent.
I get the following error message:
SQL Exectution error,
Exectuted SQL statement: SELECT...
Source: .Net SqlClient data provider
Message: Timeout expired, timeout period elapsed prior to completion of the operation...
The view is operating on a table of 2mil records. The timeout occurs after 30 seconds, and none of the changes I make to the various timeout settings in the server or database seem to affect this.
When I execute the same sql statement in a query window it does complete, requiring about 40 seconds to execute.
How can I configure the view not to timeout when executing this view?
Hi,
I am getting an time out expired error while import dbf files to the database.. In this upload one file had 379 records.. and it inserts it into the few tables and then i get the above error..in my event viewer.
Error: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
No Changes made to the Plan table.
Inserting records(s) in Plan table.
No Changes made to Plan table.
Updating changes to PlanStatementInfo.
Updated 1 record(s) in PlanStatementInfo.
Inserting new records into PlanStatementInfo.
No new records were added to PlanStatementInfo.
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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)
at icc.BaseClasses.DL.DLImportPlan.Import(Int32 ClientId, Int32 PeriodId, Int32 UserId) in C:Documents and SettingsMy DocumentsPlanStatementsImportDLDLImportPlan.cs:line 116
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.cs:line 116 --this is where i am calling my sproc...
any help will will appreciated
Thanks,
Karen
We have been bothered with this problem for a while. Usually I happens in the early moring. Later on after the error is gone on auser, the error never happens again on any user for the day. Is this a web Server problem or an aspx.vb coding error? Thanks,Jeffrey
Server Error in '/SSSSS' Application.
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.Source Error:
Line 270: oDBCommand.Connection.Open()
Line 271:
Line 272: Dim myReader As SqlDataReader _
Line 273: = oDBCommand.ExecuteReader(CommandBehavior.CloseConnection)
Line 274:Source File: E:SSSSSScheduling.aspx.vb Line: 272 Stack Trace:
[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +862234
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739110
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1956
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +31
System.Data.SqlClient.SqlDataReader.get_MetaData() +62
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +903
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +122
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +62
Soma.Scheduling.GetNextAutoAppointment() in E:SSSSSAScheduling.aspx.vb:272
Soma.Scheduling.Page_Load(Object sender, EventArgs e) in E:SSSSSScheduling.aspx.vb:61
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Hi All,
I have the same question and error that Chopaka is getting:
"I have a SQL 2005 job that calls a stored proc. The job step returns the message "Query timeout expired....Message 7412...The step succeeded." The proc never actually ever did anything due to the query timeout, and the job continued on to other steps. I'm going to address the timeout issue eventually, but first I'd like to trap the timeout problem and force the job to end.
It appears that the query timeout isn't really an error, just a message. I've tried TRY-CATCH in the SP but the situation isn't caught, again probably due to the interpretation that it isn't an error."
I have reduced the "Remote Query time out" to 1 sec, in order to catch the error and to prevent the job from running, but the error is not caught.
Is there a way to catch this in the SQL or in the job step to prevent the job from continuing?
This is the script that I'm using without any luck
BEGIN TRY
BEGIN Transaction
Create table #tmpSummaryTable
(
)
insert into #tmpSummaryTable
select * from CDRServer01.iXtemp.dbo.gx_tbFTRSummary_test
COMMIT Transaction
END TRY
BEGIN CATCH
DECLARE @err int
SELECT @err = @@error
PRINT '@@error: ' + ltrim(str(@err))
SELECT ERROR_NUMBER() ERNumber,
ERROR_MESSAGE() Error_Message
ROLLBACK
Return
END CATCH
Hello,I have one application which is having written in asp.net & plain asp.I am having one button on asp page,when i will click on that button, then itwill execute one other asp page.And after the execution of that second asp page, I redirect it to someASPX page with some values.On the ASPX page, it will connect to the Database, and insert the values.Thus, sometime, the following error is occuring :"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."Main thing is that i am testing it on my local machine, then also it is giving me this error ...Insert into statement is also not much complicated :just I inserted three values in one table.Is this occuring due to the mixer of asp & aspx??Plz give me some proper solution.I want it in efficient manner, because this application will be accessed by number of users at the same time.Plz help me.Thanks,Sandy
View 3 Replies View RelatedHi All,
I've had a DTS Package scheduled to run every morning since June last year, however on Monday and again this morning, the DTS package has failed on two of its steps. This DTS package runs on SQL Server 2000 and the server is a Windows 2000 Server.
Basically, the DTS Package steps that fail are populating a "cache" table from a "live" table and then performing Inserts / Updates on the "live" table from a CSV file depending upon whether data exists in the "cache" table and whether the CSV file contains an "Insert" or "Update" flag. The live table has just over 800,000 rows of data and our nightly CSV extract, containing both inserts and updates, has about 6000 rows.
The error / failure has only happened in the last two days and I'm not too sure if there's any "timeout" feature in DTS and if there is, how I can modify it, or whether this may be something to do with long transactions or temp dbspace running out.
The time that the DTS package runs was modified last week to run two hours earlier (03:00 instead of 05:00) and has ran okay for a few days. I don't know whether this change is a red herring, as I have checked other DTS packages on the machine and none appear to run at the same time.
Here's the message from the third step in the DTS Package (second one that's failing).
Executed as user: SOEincaservice. ...
Start: DTSStep_DTSExecuteSQLTask_1
DTSRun OnStart: DTSStep_DTSExecuteSQLTask_10
DTSRun OnError: DTSStep_DTSExecuteSQLTask_1,
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
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1
DTSRun OnError: DTSStep_DTSExecuteSQLTask_10,
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: Micros... Process Exit Code 2.
The step failed.
Any help is greatly appreciated as I've searched these forums and the web and can't really find any answers.
Cheers,
David
Server Error in '/' Application.
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. 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.InvalidOperationException: 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.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[InvalidOperationException: 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.]
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +1188873
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +413
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
DataCaoZuo.Manage_ResultTB_Caozuo(String comstr) +145
Cls_UserManage.GetAllUserList() +18
Index.Page_Load(Object sender, EventArgs e) +83
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
Ok bear with me here :). I have a server that is getting about 1000000 hits per day with about 10,000 unique vistors. For the past 2 months I have been revamping my code trying to deal with the increase in traffic. I have 2 boxes, one for the website, and one for the SQL. They are connected through a secure backlink so that I dont have to worry about encrypting the data. So the problem started when I updated the MDAC components a few weeks ago. I started getting these freaking timeout errors, they are up to about 1000 errors per hour. I have been monitoring the connection pooling using the system monitor for about a week and have noticed that I am not maxing out the pooling but I am still dropping connections. I went into the web.config and turned my max connections to 1000. Unfortunately this didn't even put a dent in the problem. It doesn't matter if I have 12 or 212 open connections it still drops them. I am at my wits end with trying to debug this problem. I am wondering if anyone else has had similiar problems recently. Also on a side note I have checked all my connections to make sure that I am closing them. Not only do I close my datareaders but I also set them to nothing. In addition to closing and reseting my datareaders I am also disposing and reseting my connection objects as well as closing them. Any help would be greatly appreciated.
Thanks,
Daniel Christoffersen