- Primeros pasos
- Comprender UiPath Robot
- Asistente de UiPath
- Requisitos de instalación
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Configuración de Windows Server para robots de alta densidad
- Redirección de Robots a través de un servidor proxy
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Configuración de los robots Linux
- Configuración de Verificación de la firma de paquete
- Configurar carpetas de paquetes y rutas de red
- Configurar fuentes de actividad
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integraciones
- Solución de problemas
Solución de problemas de conexión
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:
-
En Orchestrator, ve a Tenant > Configuración > Seguridad y luego selecciona Permitir tanto autenticación de usuario como autenticación de clave de robot.
To connect using your machine key instead, go to the sign-in screen in Studio, then select More Options > Connect to Orchestrator.
The Robot is installed in Service Mode. To use the interactive sign-in feature, you must install the Robot application in User Mode.
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.
Your user account is not properly configured to acquire a license from Orchestrator.
The user connected with the machine key associated with one tenant, but then tries to sign in to a different tenant.
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.
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.
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.
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.
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.
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).
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:
-
Se utiliza una clave de máquina o ID de cliente/secreto de cliente para la conexión y las credenciales de robot unattended en Orchestrator no coinciden con ningún usuario de la máquina.
-
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.
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.
-
Check if the robot configuration in Orchestrator is correct and an attended license is available.
-
Desconéctate y vuelve a conectarte a Orchestrator, ya sea mediante la clave de la máquina o con el registro interactivo.
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.
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.
Soluciones:
-
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.
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.
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.
Este código de error se aplica a las conexiones URL de servicio.
Error message: There are no available licenses on the server.
Connection status: Connected but unable to retrieve a license.
-
El tenant de Orchestrator al que está conectado el robot no tiene licencias disponibles.
-
El usuario solo tiene asignada una licencia unattended y utiliza el inicio de sesión interactivo para conectarse a Orchestrator, lo que depende de una licencia attended.
-
El usuario solo tiene una licencia asignada y está utilizando dos máquinas diferentes.
-
Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Orchestrator: Admin > Tenants > Edit license allocation.
-
En su lugar, utiliza la clave de la máquina: asegúrate de que todos los requisitos están correctamente definidos en Orchestrator.
-
If the user already has an attended license assigned, make sure Enable user to run automations option is enabled.
-
Para utilizar una sola licencia en dos máquinas, debes desconectar la primera antes de conectar la segunda.
Este código de error se aplica a las conexiones de clave de la máquina.
Error message: There are no available licenses on the server.
Connection status: Connected but unable to retrieve a license.
-
El tenant de Orchestrator al que está conectado el robot no tiene licencias disponibles.
-
El usuario solo tiene una licencia asignada y está utilizando dos máquinas diferentes.
-
Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Orchestrator: Admin > Tenants > Edit license allocation.
-
Para utilizar una sola licencia en dos máquinas, debes desconectar la primera antes de conectar la segunda.
Error message: Cannot acquire licenses because the machine licensing is turned off.
Connection status: Connected, unlicensed.
Potential issue: The machine used to connect the Robot to Orchestrator is disabled.
Solution: Enable the machine used to authenticate the Robot against Orchestrator, as described in Enabling/Disabling a Machine.
Connection status: -
Potential issue: This license has been restricted due to Export Control Restrictions.
Solution: Revisit the rules for export control. If the problem persists, reach out to support.
- El inicio de sesión interactivo no está habilitado para este tenant
- Descripción
- Posible problema
- Solución
- La conexión interactiva no está disponible
- Descripción
- Posible problema
- Solución
- El Robot no existe
- Descripción
- Posible problema
- Solución
- No se puede adquirir una licencia
- Descripción
- Posible problema
- Solución
- Ese host no es conocido
- Descripción
- Posible problema
- Solución
- You are not authorized to perform this action
- Descripción
- Posible problema
- Solución
- Licensing errors
- 1002
- 1203
- 1230
- 1232
- 1247
- 1415
- 1420
- 1431
- 1900
- 1905
- 1908
- 1912
- 1913
- 1914
- 1921
- 1927
- 1931