Solução de problemas do Serviço de Robôs da UiPath

Sem Conexão com o Serviço de Robôs da UiPath

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.

Problema potencial	Solução
O Serviço de Robôs da UiPath não está em execução.	Manually start the Robot service: Open the Services window. Select the `UiPathRobotSvc` service. Select Start.
O Serviço de Robôs da UiPath demora muito para iniciar.	O Windows reporta serviços que não carregam em um tempo especificado. Por padrão, esse valor de tempo limite é de 30 segundos, o que pode ser insuficiente para o Serviço de Robôs da UiPath. Para aumentar esse valor, você precisa: Abrir o Editor de Registro do 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. Digite ServicesPipeTimeout como o nome do novo valor. Double-click the ServicesPipeTimeout DWORD value. The Edit DWORD (32-bit) Value window is displayed. Na seção Base, selecione a opção 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.
A máquina do Robô tem permissões incorretas. Neste caso, o Serviço de Robôs da UiPath também pode aparecer como em execução.	As permissões para os serviços são concedidas a partir do Editor de Registro do Windows, da seguinte maneira: Abrir o Editor de Registro do 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. Selecione o usuário no qual você está conectado, na seção Grupo ou nomes de usuários. Habilite a opção Permitir para Controle Completo na seção Permissões. Isso concede as permissões necessárias para o Robô. Select Apply and OK to confirm the changes, then close the window. Restart the system for the changes to take effect.

Erros ao Executar como Administrador

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.

Problema potencial

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.