04 June 2008

Running SSIS package on SQL Server Agent

A SSIS package can be executed using SQL Server agent.

To execute the package a Proxy Account and a credential must be configured in SQL Server.


1) Executed as user: DOMAIN\user. The process could not be created for step 1 of job 0xB013D0354C8CBD46B79E948740EF5441 (reason: 1314).  The step failed.

The error 1314 is "A required privilege is not held by the client".

This message indicates that the SQL Server Service account doesn't have the required rights to switch the security context to the proxy account.

To fix it verify:

1) The proxy account have the "Act as part of the operating system" privilege.

2) The SQL Server Account is in the group


3) The Proxy account is in the group



Anonymous said...

a little correction:
2) The SQL Server AGENT Account is in the group...


Rui said...

It is the SQL Server Account and not the the SQL Server AGENT Account that must be in that group.
At least on my environment...

bond said...

One more requirement (at least in MS SQL 2008):

SQL Server Agent Account must have 'Adjust memory quotas for a process' (or 'Increase quotas' in pre-Windows 2003) privilege on SQL Server

Arun Kumar said...

Learn more about programming SSIS packages in C# .net and VB .net from the below link:

Vijay said...

In my case, I had to change SQL Server Agent Log As account to local and switch it back using SSCM to fix the problem. Please refer to http://vijredblog.wordpress.com/2014/06/17/a-required-privilege-is-not-held-by-the-client-the-step-failed-sql-job-fails-with-error-solution/ for more details.