Connection troubleshooting

Interactive sign-in is not enabled for this tenant

Description

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

Potential issue

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

Solution

The proposed solution must be performed by an Orchestrator administrator:

• In Orchestrator, go to Tenant > Settings > Security , and then select Allow both user authentication and robot key authentication.

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

Interactive connect is not available

Description

You cannot connect through the interactive sign-in.

Potential issue

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

Solution

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.

Robot does not exist

Description

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

Potential issue

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.

Solution

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.

Cannot acquire a license

Description

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

Potential issue

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

Solution

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.

No such host in known

Description

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

Potential issue

Connection to Orchestrator could not be established.

Solution

Make sure your Internet connection is working.

You are not authorized to perform this action

Description

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

Potential issue

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

Solution

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

Description

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

Potential issue

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

Solution

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