Troubleshooting steps for Robot connection issues with Orchestrator, including authentication errors and tenant configuration problems.

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

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

The proposed solution must be performed by an Orchestrator administrator:

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

You cannot connect through the Interactive Sign-In.

The Robot is installed in Service Mode.

When the Robot is installed in Service Mode, connect using the Machine Key first, then proceed with Interactive Sign-In (Service URL).

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

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.

The proposed solution must be performed by an Orchestrator administrator:

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

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

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

The proposed solution must be performed by an Orchestrator administrator:

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

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

Connection to Orchestrator could not be established.

Verify that your Internet connection is working.

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

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

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

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

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

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

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

When trying to connect or sign in to an Orchestrator provided with Automation Suite 2024.10, you may encounter this error: "System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception."

This issue affects Windows 10 and Mac operating systems.

Automation Suite 2024.10, which hosts the Orchestrator instance you want to connect to, uses TLS 1.3 by default. Windows 10 and Mac operating systems do not support this version.

You have two options: