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.
Error Diagnosis: When starting a process from Orchestrator, the UiPath Robot Service has the responsibility of creating the Robot User Windows session (logging the Robot onto the machine) and starting the Robot process.
In order to be able to do this, the UiPath Robot Service needs special permissions that are usually restricted to the “Local System” account on the Windows machine. If this error is encountered, it is because the account that is used to run the UiPath Robot Service does not have adequate privileges.
Important: The UiPath Robot Service is a different component then the Robot. Changing the account use to run the UiPath Robot Service does not require any changes to the Robot User account.
To diagnose the problem, do the following:
- You will need an administrator to resolve this problem.
- Open “run” and type “services.msc”.
- In services application, search for the UiPath Robot service and make sure that under the “Log On As” services column it is set to “Local System”
- If the “Log On As” column is not set to “Local System” go to the Change Log On As Setting section.
- If the UiPath Robot Service is set to “Local System”, then open a support request with UiPath.
Change Log On As Setting
- An administrator is required to resolve this problem
- Open “run” and type “services.msc”. (if not already open)
- Right click the UiPath Robot service and select properties.
- Go to the “Log On” tab.
- Select “Local System account” and click OK
- After selecting OK, right click the UiPath Robot Service again and select “Restart” in the dialog menu.
- By default, the UiPath installer will set the UiPath Robot Service to run as the “Local System” account. If the UiPath Robot Service was not using the “Local System” account, work with an admin to understand how and why it was changed.
- If the issue persists, raise support request with UiPath.