机器人服务故障排除

没有与机器人服务的连接

描述

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.

潜在问题	解决方案
机器人服务未运行。	Manually start the Robot service: Open the Services window. Select the UiPathRobotSvc service. Select Start.
机器人服务的启动时间过长。	Windows 会报告未在指定时间内加载的服务。默认情况下，此超时值为 30 秒，而机器人服务可能需要更长时间。为增加此值，您需执行以下操作： 打开 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. 输入 ServicesPipeTimeout 作为新值的名称。 Double-click the ServicesPipeTimeout DWORD value. The Edit DWORD (32-bit) Value window is displayed. 在“基数”部分中，选择“十进制”选项。 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.
机器人计算机的权限不正确。在此情况下，机器人服务也可能显示为“正在运行”。	通过 Windows 注册表编辑器向服务授予权限，如下所示： 打开 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. 从“组或用户名”部分中选择登录的用户。 在“权限”部分中，启用“完全控制”的“允许”选项。这样便可向机器人授予必要权限。 Select Apply and OK to confirm the changes, then close the window. Restart the system for the changes to take effect.

以管理员身份运行时出现错误

描述

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.

解决方案

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