June 15, 2007 at 12:53 am
Hi all,
Iam not very familiar with SQL server 2000, but one of my application runs on this. There are many packages and all are scheduled through a job. While most of them have no problem and runs as per the schedule there are few which shows errors. The problem here is when i run it manually as a package, it is succesful and the package is scheduled to run,it fails. Can anyone tell me a solution for this? please? Let me know if you need more information.
Regards,Preethi
June 15, 2007 at 1:14 am
Can you post us the error message that you get while it is executed as a job?
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
June 15, 2007 at 1:15 am
Possibly due to security. When you run the package manually, it runs under your credentials. When its scheduled it runs under the service account of SQL Agent.
It could be connections to data sources, or the file system
I'd suggest, as a first step, go to the job step that the package runs in and enable logging for that step. then you can examine the output after the package fails and see exactly what the error was.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 15, 2007 at 12:29 pm
When you view the job, does it show you the name of the DTS it is calling or is it encrypted? Regardless, at the job level there may be parameters passed to the DTS which could be the cause of failure. If they're encrypted for ease of troubleshooting you may want to locate and use DTSRunDec (google) as it will show you the actual string being passed.
Also, the following tables may help you find more information (if your DTS packages are logging):
msdb.dbo.sysdtspackagelog
msdb.dbo.sysdtssteplog
msdb.dbo.sysdtstasklog
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply