Solución de problemas de Robot Service

Sin conexión al mantenimiento de robot de UiPath

Descripción

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.

Posible problema	Solución
El mantenimiento de robot de UiPath no se está ejecutando.	Manually start the Robot service: Open the Services window. Select the `UiPathRobotSvc` service. Select Start.
El mantenimiento del robot de UiPath tarda demasiado en iniciarse.	Windows informa de los servicios que no se cargan en un tiempo concreto. De forma predeterminada, el valor de tiempo de espera es de 30 segundos, lo que puede no ser suficiente para el mantenimiento de robot de UiPath. Para aumentar este valor, debes: Abrir el Editor de registro de Windows. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control registry key, and select the Control subkey. If the ServicesPipeTimeout value is not available, create it: Right-click the Control subkey, and select DWORD (32-bit) Value from the New menu. A new blank DWORD Value is created. Escribe ServicesPipeTimeout como nombre del nuevo valor. Double-click the ServicesPipeTimeout DWORD value. The Edit DWORD (32-bit) Value window is displayed. Desde la sección Base, selecciona la opción Decimal. In the Value data: field, type in 180,000. This makes the default ServicesPipeTimeout 3 minutes. It should be enough time for all Windows services to properly load. Close the Windows Registry Editor, then restart the system for the changes to take effect.
La máquina del robot tiene permisos incorrectos. En este caso, el mantenimiento de robot de UiPath también puede aparecer como en ejecución.	Los permisos de los servicios se otorgan desde el Editor de registro de Windows, de la forma siguiente: Abrir el Editor de registro de Windows. Navigate to theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet registry key. Right-click the Control subkey, and click on Permissions. The Permissions for Control window is displayed. Selecciona el usuario bajo el cual has iniciado sesión en la sección Nombres de grupo o de usuario. Habilita la opción Permitir para Control completo en la sección Permisos. Esto otorga los permisos necesarios para el robot. Select Apply and OK to confirm the changes, then close the window. Restart the system for the changes to take effect.

Errores al ejecutarse como administrador

Descripción

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.

Posible problema

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.