January 19, 2007 at 9:27 am
We just experienced a full system crash. I have recovered my SQL server and all seems well except that my scheduled jobs that were created from Local Packages fail to run. I can manually run the Jobs within Local Packages. (These are mostly import jobs)
Other Scheduled jobs such as Database Backups, integrity checks and optimizations run fine (all SQL Created jobs) but all the jobs that I create and then schedule fail. (Except that they do run fine within local packages.) Recreating the scheduled job does not correct the issue.
As part of the recovery process, I had to reinstall Outlook and configure my mapi profile, but once I did that, then the Local Packages worked fine. (some of the jobs email queries to myself and others as a result of the imports.)
The error I get is: Executed as user: xxxxxx. The process could not be created for step 1 of job 0xC8D4CC70D6C7EB4DA5F0373395B5C8A2 (reason: The system cannot find the file specified). The step failed.
Any ideas?
January 19, 2007 at 9:48 am
I wonder if DTSRun.exe was restored to a different location. This KB article describes the error: http://support.microsoft.com/kb/322746/en-us
Greg
Greg
January 19, 2007 at 2:24 pm
Go into the Job and check:
1. On General Tab...who owns it. Do they have permissions to run it.
2. On Step tab....expand each step...is it running in the correct database.
3. On the Step>Advance tab...is the RUN as .
Lastly, check the services. What is the login used by SQLServerAgent service?
-SQLBill
January 19, 2007 at 4:12 pm
Greg Posted
I wonder if DTSRun.exe was restored to a different location. This KB article describes the error: http://support.microsoft.com/kb/322746/en-us
Greg
------------------------------------------------------------------
Thanks Greg,
That was the solution. Once I add the path to the DTSRun command the job works!
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply