Error while running job from Orchestrator(Unattended Mode) ie "Could not start executor. Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)"
Issue Description:
The error message "Could not start executor. Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)" may appear while executing the robot. This typically occurs if the user doesn't have specific privileges set on the robot machine according to the Installation Prerequisites for a Robot. This article provides a comprehensive guide for the required checks and troubleshooting methods to address this problem.
Root Cause:
Typically, the user associated with running the robot requires certain privileges. If these are not set correctly, the robot cannot function as expected. Specifically, the user must have access provided under specific policies in the Group Policy Editor:
- "Access this computer from the network" policy - Typically, this access is granted to the Users group.
- "Allow log on through Remote Desktop Services" policy - Usually, this permission is granted through the Remote Desktop Protocol (RDP) Users group.
- "Allow Log on Locally" policy - This privilege is essential for console sessions and Remote Desktop Protocol (RDP) sessions because the robot connection originates locally.
Troubleshooting Steps:
If the above privileges are correctly set and the issue persists, follow the troubleshooting steps below:
Verify if the user is present in the following policies or any other deny policy. If yes, remove the user from it:
- "Deny Access this computer from the network" policy - Typically, this is granted to the Users group.
- "Deny Allow log on through Remote Desktop Services" policy - Usually, this is granted through the RDP Users group.
By following the above checks and troubleshooting steps, any errors related to user privileges on the robot machine in UiPath should be rectified.