Unable to connect machine to Studio/Assistant with Testing license in On-Premises Orchestrator

Help Studio
1

I am currently working in an On-Premises UiPath Orchestrator environment and trying to connect a machine to UiPath Studio / UiPath Assistant using a Testing license, but I keep encountering connection errors.

Issue Description
When I try to connect the machine using the Machine Key in Studio or Assistant, I receive one of the following error messages:
“There are no available licenses on the server.” or “The robot is not configured for the current user.”
Because of this, the machine cannot be connected successfully.

Environment Details
On-Premises / Testing

Question
Are there any additional role assignments, robot configurations, or license-related settings required to connect a machine with a Testing license in an On-Premises Orchestrator?

Any guidance or similar experiences would be greatly appreciated.

Additionally, I have heard that the setup or connection process differs between Cloud and On-Premises environments, and I would like to understand why those differences exist.

Thank you in advance.

image
image756×757 65.5 KB

2

Hi @lbs927

Yes. In On-Premises Orchestrator, a Testing license alone is not enough. You must also create and assign a Robot + User + License explicitly.

Root cause (what’s happening)

  • The machine connects successfully using the Machine Key
  • But no robot is assigned to the user, or
  • No Testing license is allocated to that user/machine

What’s missing / required

  1. Create a User in Orchestrator
  • Tenant → Manage Access → Users
  • Assign roles: Automation User / Tester (or equivalent)
  1. Create a Robot (Classic or Modern – must match your setup)
  • For Classic:
    • Create Robot
    • Map Domain\Username correctly
  • For Modern:
    • Assign user to a Machine Template
  1. Assign the Testing License
  • Tenant → Licenses
  • Allocate Testing Robot license to the user (not just available in pool)
  1. Machine setup
  • Machine must be Unattended/Testing enabled
  • Machine Key must belong to the same Tenant & Folder
  1. Folder access
  • User must be explicitly added to the Folder
  • Folder must allow Testing execution

Regards
Gokul

3

Hi @lbs927

Yes. In an On-Premises Orchestrator, the user must be explicitly assigned a Testing license, the user must be added to the correct folder with roles that include Robot and Testing permissions.
the robot must be properly configured or mapped to the user (Classic or Modern folders as applicable), and the Studio/Assistant must be connected using the same user identity. These steps are mandatory in On-Premises because license allocation and user-robot associations are manual, unlike Cloud Orchestrator where they are handled automatically.

If helpful, mark as solution. Happy automation with UiPath

4

Hi @lbs927

In On-Premises Orchestrator, testing/community licenses usually cannot connect because the server requires a recognized license for robots. The errors happen because the license isn’t allocated or the robot/user isn’t configured properly.

Check that the robot is created in Orchestrator, assigned to a machine and environment, and the user has permission. Cloud handles testing licenses dynamically, but On-Prem requires a proper development or attended robot license. For testing in On-Prem, you need a temporary development license from UiPath.

5

Verify the Testing License allocation as shown in the image. Testing License access is currently missing and needs to be assigned to you.