- Release Notes
- Getting Started
- UiPath® Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Restarting Robot Components
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Robot Citrix Apps Virtualization
- Troubleshooting
- Common Connection Errors
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET required during installation
- Assembly Cannot Be Loaded From Network Or Azure File Share
- Activities cannot find .NET Runtime
Common Connection Errors
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.
- Connected but unable to retrieve a license.
- Robot does not exist
- 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.
- Connected but identified configuration issues.
- The standard machine does not have an exact match to the name of the machine the robot is installed on.
- The machine key used to connect the robot to Orchestrator is configured to work with a different standard machine.
- Check the specific information for the machine configuration in Orchestrator.
- Connected but unable to retrieve a license.
- No robot configured for the current user.
- 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.
- Connected but unable to retrieve a license.
- Could not find unattended robot for user key {0}
-
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.
- Connected but unable to retrieve a license
- Could not find robot by key {0}
- 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.
Error 191x
appears.
- Connected as Unattended.
- No runtime licenses available.
- The user is connected to Orchestrator, but does not have unattended runtimes.
- Allocate unattended licenses for the robot machine from Tenant → Machines → Runtime details → Production (Unattended).
- Connected but identified configuration issues.
- The domain/username configured in Orchestrator does not match any user on the machine.
- 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.
- 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
- Connected but unable to retrieve a license.
- Invalid authentication token.
- The authentication token used to maintain the connection to Orchestrator has expired or is no longer valid.
- Check if the robot configuration in Ochestrator is correct and an attended license is available.
- Disconnect and reconnect to Orchestrator, either through Machine Key or Interactive Sign In.
- Connected but unable to retrieve a license.
- No more
LicenseName
robots available. Please update your license!
- 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.
This error code applies to Automation Suite.
Connection Status:
- Connected but unable to retrieve a license.
- Action not possible. Valid license is required!
- The Orchestrator tenant to which the robot is connected does not have any available licenses.
This error code applies to Service URL connections.
Connection Status:
- Connected but unable to retrieve a license.
- There are no available licenses on the server.
- The Orchestrator tenant to which the robot is connected does not have any available licenses.
- User only has an unattended license assigned and uses interactive sign in to connect to Orchestrator, which depends on an attended license.
- User has only one allocated license and is using two different machines.
- Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Admin → Tenants → “Edit license allocation” icon.
-
- 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.
- To use a single license on two machines, you must disconnect the first one before connecting the second one.
This error code applies to Machine Key connections.
Connection Status:
- Connected but unable to retrieve a license.
- There are no available licenses on the server.
- The Orchestrator tenant to which the robot is connected does not have any available licenses.
- User has only one allocated license and is using two different machines.
Resolution
- Make sure that the tenant has enough licenses. Licenses can be assigned by accessing Admin → Tenants → “Edit license allocation” icon.
- To use a single license on two machines, you must disconnect the first one before connecting the second one.
This error code is displayed in Assistant.
Connection Status:
- Connected, unlicensed.
- Cannot acquire licenses because the machine licensing is turned off.
- The machine used to connect the Robot to Orchestrator is disabled.
Resolution
- Enable the machine used to authenticate the Robot against Orchestrator, as described in Enabling/Disabling a Machine.