DTS fails on job but runs manually

[Socrates]

All,

My package is failing on the sqlagent jobs but run successfully when
executed manually. The package was created using the local admin login which
is under the sql built-in admin account so I'm not sure why its failing for
the job.

Thanks for your help.

Costa

[Russell Fields]

Costa,

When executed by the SQL Agent your DTS package runs as the local admin
account. When you run it, it runs as your login. Therefore, your login has
rights to something that the local admin account does not.

Note that the local admin account is "local" and is not good for accessing
files on the network, other servers, and so forth. A DTS package is often
making use of resources outside the machine where the SQL Server runs.

Recommendation: Your SQL Server should not be running as local admin, but
as a domain account that has been granted the needed rights on the SQL
Server as well as other domain rights that are necessary to your job.

RLF

Post by Socrates
All,
My package is failing on the sqlagent jobs but run successfully when
executed manually. The package was created using the local admin login which
is under the sql built-in admin account so I'm not sure why its failing for
the job.
Thanks for your help.
Costa

[Socrates]

Russell thanks for you help you pointed me in the right direction.

Basically the issue was that the sql account did not exist on my destination
server. Since it is a local account I had to inpersonate it so that windows
thinks it the same. Per your advise the true solution is to have sql run on a
domain account to avoid network issues.

Thanks for taking a look; really appreciated.

Post by Russell Fields
Costa,
When executed by the SQL Agent your DTS package runs as the local admin
account. When you run it, it runs as your login. Therefore, your login has
rights to something that the local admin account does not.
Note that the local admin account is "local" and is not good for accessing
files on the network, other servers, and so forth. A DTS package is often
making use of resources outside the machine where the SQL Server runs.
Recommendation: Your SQL Server should not be running as local admin, but
as a domain account that has been granted the needed rights on the SQL
Server as well as other domain rights that are necessary to your job.
RLF

Post by Socrates
All,
My package is failing on the sqlagent jobs but run successfully when
executed manually. The package was created using the local admin login which
is under the sql built-in admin account so I'm not sure why its failing for
the job.
Thanks for your help.
Costa