- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Robot Service troubleshooting
Sometimes you might not be able to start an automation, no matter if the Robot Service is on or off. Manually starting the automation displays the following error message: "Get settings from service failed, reason System.Exception: Could not connect to UiPath Robot Service.".
The following solutions may need to be implemented by your network administrator.
Potential issue |
Solution |
---|---|
The Robot Service is not running. |
Manually start the Robot service:
|
The Robot Service takes too long to start. |
Windows reports services which do not load in a specified time. By default, this timeout value is 30 seconds, which can be insufficient for the Robot Service. To increase this value, you need to:
|
The Robot machine has incorrect permissions. In this case, the Robot Service might also appear as running. |
Permissions to services are granted from the Windows Registry Editor, as follows:
|
Starting with version 2020.4, running UiPath Assistant or Studio as an administrator could block the communication with the Robot Service. The following issues may occur:
-
In Studio - the Robot Status displays a "Robot Error" message, and when trying to run or debug a process, an "Access Denied" error is displayed.
-
In Assistant - the connection statust is incorrectly reported offline and the process list is not available.
Studio and Assistant must communicate with the Robot Service, which is a separate Windows process. The Robot Service starts up at the same level of access rights as the Assistant or Studio, which ever calls the service first.
The issue arises when you start the Assistant or Studio at different levels of access rights, such as a normal user and then as an administrator. For example, say the Assistant starts as a normal user, and then you restart it as an administrator. The Robot Service, specifically the User Host service, which was started at the normal user level, is unable to communicate with the Assistant running at the administrator level.