Fehlerbehebung für die Verbindung

Interaktive Anmeldung ist für diesen Mandanten nicht aktiviert

Beschreibung

The tenant you are trying to access does not have authentication enabled.

Mögliches Problem

The tenant might have been created in an older version of Orchestrator, prior to the implementation of the interactive sign-in feature.

Lösung

The proposed solution must be performed by an Orchestrator administrator:

• Wechseln Sie in Orchestrator zu Mandant > Einstellungen > Sicherheit, und wählen Sie dann Benutzerauthentifizierung und Roboterschlüsselauthentifizierung zulassen aus.

To connect using your machine key instead, go to the sign-in screen in Studio, then select More Options > Connect to Orchestrator.

Interaktive Verbindung ist nicht verfügbar

Beschreibung

You cannot connect through the interactive sign-in.

Mögliches Problem

The Robot is installed in Service Mode. To use the interactive sign-in feature, you must install the Robot application in User Mode.

Lösung

Reinstall the Robot in the User Mode.

To connect using your machine key instead, go to the sign-in screen in Studio, then select More Options > Connect to Orchestrator.

Der Roboter ist nicht vorhanden

Beschreibung

You receive the error message "Robot does not exist".

Mögliches Problem

You might be using a classic robot, which was defined in Orchestrator using the classic method or via the Windows user, and you are already connected to Orchestrator with a machine key. When you then sign in from Studio, a different username is sent to Orchestrator.

Lösung

The proposed solution must be performed by an Orchestrator administrator:

• In Orchestrator, set up a modern robot, then sign in again.

To connect using your machine key instead, go to the sign-in screen in Studio, then select More Options > Connect to Orchestrator.

Lizenz kann nicht erworben werden

Beschreibung

You receive the error message "Cannot acquire a license".

Mögliches Problem

Your user account is not properly configured to acquire a license from Orchestrator.

Lösung

The proposed solution must be performed by an Orchestrator administrator:

• In Orchestrator, edit the problematic user account to execute attended automations, then assign it an Attended license.

To verify the license availability, go to Tenant > License.

Ein solcher Host ist nicht bekannt

Beschreibung

You receive the error message "No such host in known".

Mögliches Problem

Eine Verbindung mit Orchestrator kann nicht hergestellt werden.

Lösung

Stellen Sie sicher, dass Ihre Internetverbindung funktioniert.

You are not authorized to perform this action

Beschreibung

You receive the error message "You are not authorized to perform this action".

Mögliches Problem

The user connected with the machine key associated with one tenant, but then tries to sign in to a different tenant.

Lösung

For User Mode installations, sign in using the service URL.

For Service Mode installation, sign out from the Assistant, then sign in again.

Could not start executor in an RDP setup

Beschreibung

You receive the error message "Could not start executor. RDP connection failed: Message: The connection transport layer failed. Last error: 131085".

Mögliches Problem

The user account used to run the unattended automation runs was not added to the Remote Desktop Users group.

Lösung

Add the user account to the Remote Desktop Users group. For details, see User permissions to run automations.