CODEWITHSUNDEEP
sql-serverssissql-server-agent
kickinchicken
kickinchicken

Reputation: 1625

SQL Server Agent job not running package

I have an SSIS package that I have deployed to the file system. The owner for the package is my Windows Login. The reason for this is that it needs to write files to another server. If I make the owner NT SERVICE\SQLSERVERAGENT the error that I get is that the files on the remote server cannot be accessed.

The package itself runs under my account. The package normally takes about 5 minutes to run and works when run directly (double click, click Execute and enter decryption password). I can tell the package has run because it writes a number of logs to the file system.

I've set up a SQL Server job to run the package. The job says it's run successfully but there are no logs being written. I'm not sure where I've gone astray other than there's some account that I'm likely missing.

Has anyone else ever run into this?

Upvotes: 1

Views: 1197

Answers (1)

kickinchicken
kickinchicken

Reputation: 1625

The issue was that I needed to set up a proxy Account to run the SQL Server agent.

Upvotes: 1

Related Questions