Skip to main content
Question

Unable to assign Bot Creator license despite 2 available licenses

  • March 24, 2026
  • 2 replies
  • 14 views

Hi,

I am trying to assign a Development / Bot Creator license to a user in Control Room, but I get the following error message:

'Environment: Automation Anywhere Control Room Symptom: available licenses are displayed, but assignment fails with featurelicenseexceeded'

What is strange is that the interface still shows that 2 Bot Creator licenses are available.

Has anyone seen this issue before?

I would appreciate any advice on how to troubleshoot this.

Thank you

2 replies

Hi ​@NinaNicolas ,
 here's what I figured out after going through this myself -

The most common reason this happens is that those licenses are already silently allocated somewhere else. If your setup has multiple Control Room environments (like a Dev, UAT, and Prod), those same Bot Creator licenses might still be "checked out" against another environment even though they look free on your current one. Go into each of those environments, find the user under Administration > Users, edit them, and explicitly set the device license to None and save. Once you do that properly, the license actually frees up correctly.

Second thing to check - look at the role assigned to this user. Your own screenshot actually gives this away! The dialog box says "Device licenses are only applicable if the user does not have the Administrator role." So if the user you're trying to assign to happens to have the AAE_Admin role or any system admin privileges, the Control Room gets confused about the license assignment. Go check the user's Roles tab and see if that's the case.

Third thing - inactive or deleted users sometimes hold onto licenses without anyone realizing. Someone probably got removed from the system but the license wasn't released beforehand. Go through your full user list including inactive ones under Administration > Users and check if anyone still has a Bot Creator license sitting against their name unnecessarily.

And lastly - if you're on an on-premise setup, sometimes the Control Room's local license count just gets out of sync with what the actual license server sees. A Control Room service restart usually forces it to re-sync and the count corrects itself.

Honestly, start with the first one - checking other CR environments. That's fixed it for me and a few colleagues about 80% of the time. The license just needs to be properly released from the other end.

Let me know how it goes - happy to help further


  • Author
  • Ground Control | Tier 1
  • March 25, 2026

Hi,

Thanks for your message.

I already checked all of that carefully. We do have the correct number of licenses allocated (see screenshot) in the two other Control Rooms, but despite that, I’m still unable to assign a license to them.

I also verified that they do not have any admin role assigned (see screenshot of the 3 control rooms)

At this stage, everything seems to be configured correctly, but the issue is still happening…

 

Thank you for your help