(New to SSIS. None of the similar questions mention this particular impersonation error.)
I'm trying to run an SSIS package as an Agent job via a proxy, and I'm getting a non-helpful error message. The credential object is for an AD account. I'm able to log in with the password to other services, but attempting to run the Agent job errors out in the Execute job step. Running the job as SQL Agent service account worked, but it doesn't have access to the filesystem that the SSIS job is supposed to pull data from.
I checked the agent log file and it's this:
 SQLServer Error: 22046, Impersonation error. [SQLSTATE 42000]
I checked the Windows security log in Event Viewer:
Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xC000006D Sub Status: 0xC000006A
I tried it with my (sysadmin) user ID and password in a different credential / proxy and got the same error. I know that account works.
We granted both SQL Agent and this account user rights to logon as batch job, and the agent account permission to impersonate. We also tried making the various accounts Windows admins and sysadmins, but nothing has helped.
This worked right out of the box in our QA domain.
Any suggestions how to get this to work? What domain/local/SQL Server security settings would enable or prevent the agent impersonating a user?
Windows 2016 + SQL Server 2016