March 23, 2005 at 8:53 am
I received the following error in a DTS job that has run successfully ever night for a year, until last night:
Executed as user: CMS-DB\Admin. DTSRun: Loading... 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. Process Exit Code 1. The step failed.
The job has two steps. The first step, which just runs a batch job to delete a log file, completed successfully. The first task in the failed second step is to clear out (truncate, delete) some permanent database tables that are about to be refreshed. This task did not occur. All of the tables are on the same server as the DTS job.
Any ideas what may have caused this, or things I should look at? The job will run again tonight (or not), so I can see if a pattern develops, but if there's something I need to change, I'd rather do that than wait for the job to fail again.
Thanks,
Mattie
March 24, 2005 at 1:26 am
Try setting ConnectionTimeOut = 0 for the database connection
You can do this using the disconnected edit .
1.Expand Connections
2. You can see the DB connections your package has
3. on the Right hand side you can connectiontimeout . Set it to Zero
By doing this , the Timeout error should not occur
Regards
Meghana
March 24, 2005 at 6:39 am
I'll definitely take a look at that. After further digging, we think the truncate table command that was in the timed-out task ran into an incremental backup of the files. We moved the time slightly so that it shouldn't conflict, but we all know how that goes. This would be a much better fix.
Thanks for your help.
Mattie
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply