- Erste Schritte
- Grundlegendes zu UiPath Robot
- UiPath Assistant
- Installationsanforderungen
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Einrichtung von Windows Server für High-Density-Roboter
- Weiterleitung von Robotern über einen Proxy-Server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Einrichten von Linux-Robotern
- Konfigurieren der Paketsignaturüberprüfung
- Einrichten von Paketordnern und Netzwerkpfaden
- Konfigurieren von Aktivitätsfeeds
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrationen
- Fehlersuche und ‑behebung
Robot-Administratorhandbuch
Fehlerbehebung für den Roboterdienst
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.
Mögliches Problem |
Lösung |
---|---|
Der Roboterdienst wird nicht ausgeführt. |
Manually start the Robot service:
|
Der Start des Roboterdienstes dauert zu lange. |
Windows meldet Dienste, die nicht in einer bestimmten Zeit geladen werden. Standardmäßig beträgt dieser Timeoutwert 30 Sekunden, was für den Roboterdienst vielleicht nicht ausreicht. Um diesen Wert zu erhöhen, müssen Sie:
|
Die Robotermaschine verfügt über falsche Berechtigungen. In diesem Fall wird der Roboterdienst möglicherweise auch als ausgeführt angezeigt. |
Berechtigungen für Dienste werden wie folgt über den Windows-Registrierungs-Editor erteilt:
|
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.