June 27, 2007 at 11:58 am
I have 16 DTS packages that run successfully when run manually, but when I have them scheduled as a SQL Agent Job only 2 of the DTS packages fail. So when I the failing DTS packages manually there is no way to find out why they are failing.
I am using DTSRUN /S "<Server Name" /E /N "DTS Package Name" and it works for the other 16 packages.
How can I find out why, under SQL Sever Agent these two packages fail as the message
"The job failed. The Job was invoked by Schedule 10 (DataMart - ETL Complete Step by Step Package). The last step to run was step 9 (DM Trans 9).
Anyone that could shed some light would be greatly appreciated.
June 27, 2007 at 12:27 pm
Who owns the jobs that start the packages?
Check to see if there's a difference in the context (different user) between each runs. That would be my first guess.
June 28, 2007 at 10:46 am
Steph,
Enable package logging in all your packages to get more accurate info about package failure.
To enable logging, open the package in DTS Designer, select package properties, and the Logging tab. Check the box next to "Log package execution to SQL Server and make sure the server is set ot "Local" or the name of the server where the package runs. Save the package.
When the package fails, right click on the package in Enterprise Manager and select "Package Logs...". Open the log for the failed run to see error messages.
Greg
Greg
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply