- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Connection troubleshooting
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:
-
In Orchestrator, go to Tenant > Settings > Security , and then select Allow both user authentication and robot key authentication.
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.
- Interactive sign-in is not enabled for this tenant
- Description
- Potential issue
- Solution
- Interactive connect is not available
- Description
- Potential issue
- Solution
- Robot does not exist
- Description
- Potential issue
- Solution
- Cannot acquire a license
- Description
- Potential issue
- Solution
- No such host in known
- Description
- Potential issue
- Solution
- You are not authorized to perform this action
- Description
- Potential issue
- Solution