Résoudre les problèmes du service de robot UiPath

Pas de connexion au service Robot

Description

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.

Problème potentiel	Solution
Le service Robot n'est pas en cours d'exécution.	Manually start the Robot service: Open the Services window. Select the UiPathRobotSvc service. Select Start.
Le démarrage du service Robot est trop long.	Windows signale les services qui ne se chargent pas dans un délai spécifié. Par défaut, cette valeur de délai d'expiration est de 30 secondes, ce qui peut être insuffisant pour le service Robot. Pour augmenter cette valeur, vous devez effectuer les opérations suivantes : Ouvrez l'éditeur du Registre 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. Tapez ServicesPipeTimeout comme nom de la nouvelle valeur. Double-click the ServicesPipeTimeout DWORD value. The Edit DWORD (32-bit) Value window is displayed. Dans la section Base (Base), sélectionnez l'option Décimal (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.
Les autorisations de la machine Robot sont incorrectes. Dans ce cas, le service Robot peut également apparaître comme étant en cours d'exécution.	Les autorisations d'accès aux services sont accordées à partir de l'éditeur de Registre Windows, comme suit : Ouvrez l'éditeur du Registre 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. Sélectionnez l'utilisateur sous lequel vous êtes connecté depuis la section Noms de groupes ou d’utilisateurs (Group or user names). Activez l'option Autoriser (Allow) de Contrôle total (Full Control) dans la section Autorisations (Permissions). Cela accorde les autorisations nécessaires au Robot. Select Apply and OK to confirm the changes, then close the window. Restart the system for the changes to take effect.

Erreurs lors de l’exécution en tant qu’administrateur

Description

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.

Problème potentiel

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.

Solution

Ensure the Robot Service, Assistant, and Studio all operate at the same privilege level.