May 28, 2004 at 9:43 am
Hello gurus!
I have a job that runs daily at 8:30 AM EST. It runs a DTS package.
Every time it runs it produces an error:
Executed as user: (SQL Agent DomainAcct masked for security purposes). ...Start: DTSStep_DTSExecuteSQLTask_9 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_9 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_3 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_3 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_5 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_5 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_4 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_4 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_8 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_8 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnError: DTSStep_DTSExecuteSQLTask_2, Error = -2147217873 (80040E2F) Error string: The statement has been terminated. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217873 (80040E2F); Provider Error: 3621 (E25) Err... Process Exit Code 1. The step failed.
However, when I test it manually it runs fine. Also, when I create alternate schedule to test it, it runs fine. Here is the output.
Executed as user: (SQL Agent DomainAcct masked for security purposes). DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_9 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_9 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_3 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_3 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_5 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_5 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_4 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_4 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_8 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_8 DTSRun OnStart: DTSStep_DTSExecuteSQLTask_2 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_2 DTSRun: Package execution complete. Process Exit Code 0. The step succeeded.
The question is why doesn't it run on a normal daily schedule? Thanks
May 28, 2004 at 11:06 am
It works when you test it manually and it works when you test it on an alternate schedule. So that means that something else is happening at the time that you are trying to run your script.
What other jobs are occuring at the time your job is scheduled? Is the database shut down? Is it being backed up? Is the network down?
I suggest taking the time to be at work when the job is normally scheduled to run. Let it run and see what else is running/happening that might cause it to fail. Also, try running it manually at that time.
Have you checked the Windows Event Viewer logs for any information?
-SQLBill
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply