April 11, 2017 at 4:19 am
I have set up and Agent Job to run an SSIS package using the Project Deployment Model. This works in our production environment but fails in OAT. The SQL Agent Service account, which is an AD account, has been made the owner of the Agent Job. The SQL Agent Service account is also a sysadmin. Despite this the agent job fails with a login failure for the SQL Agent Service account when it tries to access SSISDB.
Correct me if I am wrong, but I thought a sysadmin can do anything???
As I mentioned before, this same setup works on the Production server. Any ideas?
April 11, 2017 at 9:09 am
Okay, I found the issue. It was an error in the Agent Job configuration. The SSISDB server name property was pointing to the wrong server. That's what you get for scripting the jobs from another server and not correcting them when deploying to a new server.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply