Automation Developer license not consuming in On-Prem Orchestrator

Help Orchestrator
1

Description

Hi Team,

I have installed UiPath Orchestrator On-Prem (23.4) and activated an Automation Developer (Named User) license.

The license shows Activated, but it is not consuming:

Under Tenant → License → Automation Developer, user shows Unlicensed

UiPath Studio says:
“Connected to Orchestrator but unable to retrieve a license”

While connecting Studio/Assistant I get:
“Machine key is linked to another machine”

I also see only autogen\admin_local user and I don’t know which email account was used for the Automation Developer license.

Questions:

Is a real email user mandatory to consume Automation Developer license?

How to fix machine key linked to another machine?

Can autogen\admin_local consume Automation Developer license?

Please help.

Thanks!

Link

https://docs.uipath.com/studio/standalone/2023.4/user-guide/signing-in-to-your-account#common-sign-in-errors

Date

2025-12-26

2

HI @Samkaran_G
Welcome to the Community

Automation Developer is a Named User license. It must be assigned to a real user (email). admin_local cannot consume it. Create a real user, assign the license, remove old machine key, and sign in to Studio using that user.

If Solution helps you please mark as solved and let me know if u still face issue
Thanks & Happy Automations

3

@Samkaran_G

If you need a developer license then in assistant first you need to use sign in option to connect instead of clientid/machine key to connect

please try sign in and also make sure in orchestrator automation developer role is assigned to the same user you use to sign in

cheers

4

Hi @Samkaran_G

You need a real UiPath user account (email) to consume an Automation Developer license—autogen\admin_local can’t use it.

The “Machine key is linked to another machine” error means the key was already used elsewhere. Fix it by generating a new machine key in Orchestrator and connect Studio/Assistant with that new key.

After this, Studio should retrieve the license properly.

5

Hi @Samkaran_G,

Delete the standard machine and create a machine template. templates ignore the specific hostname and allow any machine using that key to connect

6

Hi @Samkaran_G

If solution help you please mark as solution so it’s help other to

Thanks

7

Hello Nishi,

Thank you for following up.
The issue has been resolved, and UiPath Studio is now working as expected. No further assistance is required currently.

Best regards,
Saravanan