Windows Job ends with Error code '1314 (= A required privilege is not held by the client.)'
search cancel

Windows Job ends with Error code '1314 (= A required privilege is not held by the client.)'


Article ID: 87471


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :
U2001000 Job '' could not be started. Error code '1314 (= A required privilege is not held by the client.)'.

A Windows job ends with the error message described above.


OS: Windows
OS Version: N/A


Cause type:
Root Cause: Local rights are missing on the OS layer.


Check the permissions for the user starting either the agent or the service manager.
Check the logon= setting in the agent's ini file.
1) The user who starts the agent or the service manager needs to explicitly have the following permissions (Found under "User Rights Assignment" in the "Local Security Settings on Windows):

Act as part of the operating system
Adjust memory quotas for a process
Allow log on locally
Back up files and directories **)
Logon as batch job *)
Logon as service
Replace a process level token
Restore files and directories
*) This right is only required if you start jobs by using the start option "logon as batch user".

**) This right is necessary for the execution of job objects.
For the extended File Transfer object (as of v9) this right is usually optional. It is necessary, however, when the agent transfers encrypted files with a file transfer because the agent uses the WinAPI "LoadUserProfile".

PLEASE NOTE: These cannot be implied through the group the user belongs to having the rights, the user itself must have the rights explicitly.

2) Be sure that the logon= setting in the Agent's ini file is set to logon=1

Fix Status: No Fix

Fix Version(s):

In addition to the steps listed above it is also recommended to deactivate UAC (User Access Control).

This can be done via Control Panel --> User Accounts --> Change User Account Control settings


The definite way to deactivate the UAC is through the following registry key:

regedit --> HKEY_LOCAL_MACHINE --> SOFTWARE --> Microsoft --> Windows --> CurrentVersion --> Policies --> System --> EnableLUA

Change the value data from 1 to 0.

This automatically prompts for a reboot of the Windows server.

Additional Information

Workaround :