robot

2024.10

true

Admin Guide

Last updated 21 oct. 2024

Résolution des problèmes de connexion

La connexion interactive n’est pas activée pour ce locataire

Description

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

Problème potentiel

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:

Dans Orchestrator, rendez-vous sur Locataire > Paramètres > Sécurité, puis sélectionnez Autoriser à la fois l’authentification de l’utilisateur et l’authentification des clés de robot.

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

La connexion interactive n’est pas disponible

Description

You cannot connect through the interactive sign-in.

Problème potentiel

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.

Le robot nʹexiste pas.

Description

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

Problème potentiel

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.

Impossible d’obtenir une licence

Description

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

Problème potentiel

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.

Aucun hôte de ce genre n’est connu

Description

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

Problème potentiel

Impossible d'établir la connexion à Orchestrator.

Solution

Assurez-vous que votre connexion Internet fonctionne.

You are not authorized to perform this action

Description

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

Problème potentiel

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.

Licensing errors

1002

Error message: Robot does not exist.

Connection status: Connected but unable to retrieve a license.

Potential issue: 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

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

Connection status: Connected but identified configuration issues.

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

Solution: Check the specific information for the machine configuration in Orchestrator.

1230

Error message: No robot configured for the current user.

Connection status: Connected but unable to retrieve a license.

Potential issue: There is no robot configured for the user that attempted to connect to Orchestrator.

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

1232

Error message: Could not find unattended robot for user key {0}.he are insufficient attended licenses, and the robot switches to unattended licenses.

Connection status: Connected but unable to retrieve a license.

Potential issue: The are insufficient attended licenses, and the robot switches to unattended licenses.

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

1247

Remarque :

This error may occur just before Error 191x appears.

Error message: Could not find robot by key {0}.

Connection status: Connected but unable to retrieve a license.

Potential issue: The robot user is disabled in Orchestrator, so the corresponding Client Credentials are no longer valid.

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

1415

Error message: No runtime licenses available.

Connection status: Connected as Unattended.

Potential issue: The user is connected to Orchestrator, but does not have unattended runtimes.

Solution: Allocate unattended licenses for the robot machine from Orchestrator: Tenant > Machines > Runtime details > Production (Unattended).

1420

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

Connection status: Connected but identified configuration issues.

Potential issues:

Une clé de machine ou un ID client/un secret client est utilisé(e) pour la connexion, et les informations d'identification de l'Unattended Robot dans Orchestrator ne correspondent à aucun utilisateur sur la machine.
The user does not use a specific Windows user account.

Solution: Check the specific information for the user in Orchestrator: Tenant > Manage Access > Edit user > Unattended setup > Domain/Username.

1431

Error message: Invalid authentication token.

Connection status: Connected but unable to retrieve a license.

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

Solutions :

Check if the robot configuration in Orchestrator is correct and an attended license is available.
Déconnectez-vous et reconnectez-vous à Orchestrator via une clé machine ou une connexion interactive.

1900

Error message: No more <License Name> robots available. Please update your license!

Connection status: Connected but unable to retrieve a license.

Potential issue: 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.

Solution: Verify the license allocation from the admin panel in Automation Cloud.

1905

Error message: Update Failed: Please Disconnect Some Machines To Match The Number Of Defined Licenses.

Connection status: -

Potential issue: There is a mismatch between the updated license and the license Orchestrator expects. For example, upon updating the license, from a total of ten runtimes in the license, the user transfers five from Unattended to Citizen Developer. However, Orchestrator expects 10 available runtimes, and thus, this error occurs.

Solutions :

Remove the existing license, select the Activate Online option, then provide the license code again.
Remove the unattended robot from the Robots page in Orchestrator, then on the Licenses page in Orchestrator, select the Update option. This updates all runtimes.

1908

Error message: Please remove some Development Robots to match the number of defined licenses.

Connection status: -

Potential issue: This error occurs when updating the license, if the number of the available runtimes does not match the active runtimes.

Solution: Remove the active runtimes from their users, update the license, then allocate runtimes back to users, based on the updated license offer.

1912

Remarque :

This error code applies to connections to Automation Suite Orchestrator.

Error message: Action not possible. Valid license is required!

Connection status: Connected but unable to retrieve a license.

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

Solution: Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Admin > Tenants > Edit license allocation.

1913

Remarque :

Ce code d'erreur s'applique aux connexions d'URL de service.

Error message: There are no available licenses on the server.

Connection status: Connected but unable to retrieve a license.

Potential issues:

Le locataire Orchestrator auquel le Robot est connecté ne dispose d'aucune licence.
L'utilisateur dispose uniquement d'une licence Unattended attribuée et utilise la connexion interactive pour se connecter à Orchestrator, qui dépend d'une licence Attended.
L'utilisateur ne dispose que d'une seule licence attribuée et utilise deux machines différentes.

Solutions :

Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Orchestrator: Admin > Tenants > Edit license allocation.
Utilisez la clé de machine à la place : assurez-vous que toutes les exigences sont correctement définies dans Orchestrator.
If the user already has an attended license assigned, make sure Enable user to run automations option is enabled.
Pour utiliser une seule licence sur deux machines, vous devez déconnecter la première avant de connecter la seconde.

1914

Remarque :

Ce code d'erreur s'applique aux connexions de clé de machine.

Error message: There are no available licenses on the server.

Connection status: Connected but unable to retrieve a license.

Potential issues:

Le locataire Orchestrator auquel le Robot est connecté ne dispose d'aucune licence.
L'utilisateur ne dispose que d'une seule licence attribuée et utilise deux machines différentes.

Solutions :

Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Orchestrator: Admin > Tenants > Edit license allocation.
Pour utiliser une seule licence sur deux machines, vous devez déconnecter la première avant de connecter la seconde.