I have been having trouble running a simple SSIS package using a Proxy account. The package always works when I run it from within Visual Studio but consistently fails when I run it from SSMS as a job step using a proxy.
I have an SSMS job with a single step: to run the SSIS package. In the "Run as:" dropdown, the package runs successfully when I choose the "SQL Server Agent Services Account", but not as "TestProxy", which I created. I also created a credential, called "Test_Credential", and gave it my own account's identify: a SysAdmin role. I assigned "Test_Credential" as the credential name for "TestProxy". For TestProxy's Principals, I added everything there was to add in the three available categories: SQL Login, msdb role, and Server role. In short, in spite of my having given the proxy every privilege I know to give, the job fails. And switching back and forth, between running as"SQL Server Agent Services Account" and running as "TestProxy", I proved that something in the proxy is causing the failure.
I have a paying client for whom proxies may wind up playing a role; and I'd like to figure this out before meeting with my client again. Your feedback, as always, is most welcome.