Resolution for error thrown when starting a job from Orchestrator : “Could not start executor. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))" In older version of UiPath the error: "Executor start process failed, reason System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))” might be encountered.
Issue Description:
Initiation of a process from Orchestrator assigns the task of creating the Robot User Windows session to UiPath Robot Service. The task includes logging the Robot onto the system, and initiating the Robot process.
The UiPath Robot Service requires specific permissions to execute this assigned task. These permissions typically reside within the "Local System" account on the Windows machine. The occurrence of an error often indicates inadequate privileges of the account operating the UiPath Robot Service.
Root Cause:
The problem arises when the UiPath Robot Service operates not under the "Local System" account and the user it operates under lacks necessary permissions.
A list of the permissions the Local System has can be found in Local System Account.
Common Errors:
The common error messages related to this issue include:
- “Could not start executor. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
- "Executor start process failed, reason System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))" (Older version of Robots)
- "Could not start executor. A required privilege is not held by the client. (Exception from HRESULT: 0x80070522)"
Note: The UiPath Robot Service is a different component than the Robot. Changing the account use to run the UiPath Robot Service does not require any changes to the Robot User account.
Resolution:
- Open “run” and type “services.msc”.
- Search for the UiPath Robot service in the services application and make sure it falls under the “Log On As” services column, set to “Local System”.
- If the “Log On As” column is not set to “Local System”, follow the directions in the "Change Log On As Setting" section.
- If the UiPath Robot Service is already set to “Local System”, proceed to open a support request with UiPath.
Change Log On As Settings:
- An administrator is required to make the following changes
- Open “run” and type “services.msc”
- Right-click UiPath Robot service and select properties.
- Locate the “Log On” tab.
- Select “Local System account” and click OK.
- After clicking OK, right-click UiPath Robot Service and select “Restart” in the dialog menu.
By default, the UiPath installer sets the UiPath Robot Service to run as the “Local System” account. If the UiPath Robot Service was operating under a different account, consultation with an admin to understand the changes is advised. If the issue persists, a support request with UiPath is recommended.