Hi,

I want to schedule an SSIS package to run as a Job under SQL Server Agent.
This package runs fine when I execute it by double clicking the package and
setting associated properties, it also runs fine on my machine as a job but
when I deploy this to another server it fails...?

I've seen a couple of posts about proxies and credentials and I've tried to
go down this route too but with no success. I created a local user on the
server with full permissions on the directory where the packages are. I then
gave this user a login on the SQL server and created the user in necessary
DBs with dboowner rights. I then created Credentials for this user and then a
proxy under SSIS Package Execution for these credentials. I then changed the
step to run as this proxy...still no success...

Can someone help me out here, I really need to understand what the correct
way to do this is and also the simplest ways. Maintaining windows accounts
and SQL logins seems a bit overkill but then I'm probably mis-understanding
what is necessary.

Thanks
Neil

p.s. sorry for long post!

Hello Neil,

what is the error? It may not be permissions. It could be resources i.e.
it is looking for a directory on the server that exists on your PC.

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Hi Allan,

The problem was fixed by re-starting the SQL Agent...go figure. Quite
annoying since I spent about half a day trying different things. The error in
the job history was 'The job was invoked by AdminAccnt. The step failed' or
something similar, I've deleted the history since.

Whats the best way to 'debug' these kinds of things? I ended up disabling
steps in my package to try to isolate the problem but is there a better way
to gather error information from the SQL Agent?

Thanks

"Allan Mitchell" wrote: