Common Connection Errors

Note:

This document is intended to help administrators resolve license connectivity issues between UiPath Assistant and Orchestrator. If you do not have access to Orchestrator, reach out to your administrator instead.

When the UiPath Assistant connects to Orchestrator, the connectivity is done using the robot through either Machine Key, Client ID/Client Secret, or Interactive Sign-In.

Based on the configuration in Orchestrator and connectivity status, an error with a specific code can occur. If an error code is not found in the list below, please check the Orchestrator response code documentation.

1002

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• Robot does not exist

Cause

• This error code can appear when 2023.10 and newer robots are connected to Orchestrator 2023.4 and older. The cause of this error could be linked to error codes 1232, 1247, or 1420. For more information, see the solution for error codes 1232, 1247, or 1420.

1203

Connection Status:

• Connected but identified configuration issues.

Error Message:

• The standard machine does not have an exact match to the name of the machine the robot is installed on.

Cause

• The machine key used to connect the robot to Orchestrator is configured to work with a different standard machine.

Resolution

• Check the specific information for the machine configuration in Orchestrator.

1230

Connection status:

• Connected but unable to retrieve a license.

Error Message:

• No robot configured for the current user.

Cause:

• There is no robot configured for the user that attempted to connect to Orchestrator.

Resolution

• Make sure that the user that tries to connect to Orchestrator has a robot configured and tied to its account.

1232

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• Could not find unattended robot for user key {0}

Cause:

• This happens when the user doesn’t have enough attended licenses and does a fallback for the unattended.

Resolution

• Create a new unattended robot or re-enable the existing one, if disabled.

1247

Connection Status:

• Connected but unable to retrieve a license

Error Message:

• Could not find robot by key {0}

Cause

• The robot user is disabled in Orchestrator and the Client Credentials are no longer valid.

Resolution

• Create a new robot or re-enable the existing one, if disabled, then restart the robot instance on the machine.

Note: This error can occur just before Error 191x appears.

1415

Connection Status:

• Connected as Unattended.

Error Message:

• No runtime licenses available.

Cause:

• The user is connected to Orchestrator, but does not have unattended runtimes.

Resolution:

• Allocate unattended licenses for the robot machine from Tenant → Machines → Runtime details → Production (Unattended).

1420

Connection Status:

• Connected but identified configuration issues.

Error Message:

• The domain/username configured in Orchestrator does not match any user on the machine.

Cause:

1. A Machine key or Client ID/Client Secret is used for the connection and the unattended robot credentials in Orchestrator do not match any user on the machine.
2. The user doesn’t use a specific Windows user account.

Resolution:

• Check the specific information for the user in: Tenant → Manage Access → Edit user → Unattended setup → Domain/Username

1431

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• Invalid authentication token.

Cause:

• The authentication token used to maintain the connection to Orchestrator has expired or is no longer valid.

Resolution:

1. Check if the robot configuration in Ochestrator is correct and an attended license is available.
2. Disconnect and reconnect to Orchestrator, either through Machine Key or Interactive Sign In.

1900

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• No more LicenseName robots available. Please update your license!

Cause:

• The Orchestrator tenant to which the robot is connected does not have any available licenses for the requested type. This can occur when multiple robots share a single license.

Resolution:

• Verify the license allocation from the admin panel in Automation Cloud.

1912

This error code applies to Automation Suite.

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• Action not possible. Valid license is required!

Cause:

• The Orchestrator tenant to which the robot is connected does not have any available licenses.

1913

This error code applies to Service URL connections.

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• There are no available licenses on the server.

Cause

1. The Orchestrator tenant to which the robot is connected does not have any available licenses.
2. User only has an unattended license assigned and uses interactive sign in to connect to Orchestrator, which depends on an attended license.
3. User has only one allocated license and is using two different machines.

Resolution

1. Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Admin → Tenants → “Edit license allocation” icon.
2. • Use the machine key instead: make sure that all requirements are correctly defined in Orchestrator.
   • If the user already has an attended license assigned, make sure Enable user to run Automations from Personal automations setup is enabled.
3. To use a single license on two machines, you must disconnect the first one before connecting the second one.

1914

This error code applies to Machine Key connections.

Connection Status:

• Connected but unable to retrieve a license.

Error Message:

• There are no available licenses on the server.

Cause

1. The Orchestrator tenant to which the robot is connected does not have any available licenses.
2. User has only one allocated license and is using two different machines.

Resolution

1. Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Admin → Tenants → “Edit license allocation” icon.
2. To use a single license on two machines, you must disconnect the first one before connecting the second one.