Hello! Ihave SSIS Package that needs special permissions in network. I want to schedule SSIS running using SQL Agent. I don't want to other Jobs starts with special permissions. So, I decided to use proxy account to impersonate SSIS starting process by account with those permissions. I've perfomed following steps: 1. Create Login for the future proxy account and add it to sysadmins role. 2. Create Credential with account name and password information. 3. Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create. 4. Set Run as for step that starts my package to this proxy 5. Start my job. and I receive error "Process couldnot be created for step 1 job xxx. Reason: 1314" SQL Agent account and proxy accounts has alsoadministrators rights on SQL Server computer and rights to login as service. When I change step configuration to run as SQL Agent account job completes succesfull. What do I do wrong? Thx, Olga

If I am not mistaken, account members of sysadmin doesn't require a proxy account. That means you would be able to run your job without a proxy account.

Was this ever resolved? I have exactly the same issue and the SQL Agent job will not start using the proxythanksJonathan

Hi Olga,I think it's not related to proxy account. I have tried the steps you mentioned and it works fine on my machine. The proxy account is used in the job to run my package. The different behavior as you mentioned also indicates that the proxy account has taken effect. I believe the reason is the proxy account does not have enough privilege. Reason: 1314 means "A required privilege is not held by the client." You may check your account's permission for the reason of failure. I will start trouble-shooting by checking what's the permission the SQL Agent account has but the proxy agent hasn't if I would you. :)Please let me know if you got further questions. Thanks.Best regards,Rodge

Olga,Some questions:- Can you describe what is in your job? Are you using the SSIS subsystem?- On step2, will you be able to describe how you assign the rights to the proxy account to run SSIS?Thanks.

In case anyone else comes across this while searching. I believe the 1314 error code is because the account running SQL Agent does not have permissions to 'Replace a process level token' on the server - this can be checked by running secpol.msc and browsing the 'User Rights Assignment'. Unfortunately, I'm unable to confirm at the moment as some muppet has changed our group policy to remove my SQL Agent account from this permission (and several others!).

How would you do that "Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create..."

How would you do that "Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create..." Here is an example of creating credentials and a proxy account: http://microsoft-ssis.blogspot.com/2010/12/how-to-schedule-package-save-way-with.html Just select more options for the ActiveX and the CmdExec Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com