January 4, 2006 at 3:02 am
Hi Guys,
Can anyone tell me why a DTS package run as a job fails but succeeds when it is run manually?
cheers
January 4, 2006 at 4:56 am
My guess is that when you try to run the DTS from the enterprise manager you are logged onto that server on your local client. The DTS package is hitting a drive or other resource on the remote server that are not found on your system or if they are found on your system the file/files it is looking for are not located causing the package to fail. Whereas the job will envoke the DTS in its proper environment on the server. To run the DTS manually under conditions such as this you need to term server into the server itself.
Good luck.
January 5, 2006 at 4:06 am
Permissions are the usual suspect.
When the job is run manually it runs with that users privileges on. When it is run as a job it runs with the privileges of the SQL Server Agent or the job owner.
Cheers
J
-------------------------------------------------------------------------
Normal chaos will be resumed as soon as possible. :crazy:
January 5, 2006 at 5:45 am
thanks guys it was down to the service account not refreshed after changing it. So a reboot simply refreshed all the services and it worked. thanks again.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply