License Update Failed On Orchestrator. You Have More X Licenses Assigned To Your Tenants Than The License Limit

News Knowledge Base
1

Upgradation of license on Orchestrator failed with error messages and codes.

Issue Description:

When an Enterprise organization using On-Premise Orchestrator renewed it's license, the license has to be updated in Orchestrator UX manually to reflect updated details in Orchestrator.

While doing the update in host or individual tenant (depending on where license was activated), Orchestrator might throw error if it does not meet the licensing conditions.

Analysis: Below are the most common error messages:

  • License Update Failed, You Have More Development Licenses Assigned To Your Tenants Than The License Limit!(#1918)"
  • Update Failed. Please Disconnect Some Nonproduction Machines To Match The Number Of Defined Licenses. (#1906)
  • Update failed! Please remove some Development robots to match the number of defined licenses. (#1908)

These error message slightly vary based on which type of license is above it's limit and the reason for these errors are described in the error message that you have defined more Attended/ Unattended/ non production/ Studio/ etc then the available quantity in your renewed license key.

    Sample Screenshot of error:


    Resolution:

    1. Release the extra license by deallocating the license from User or Robots
    2. Update the license from Orchestrator UX
    3. Allocate the license again to Users/ Robots


    Consider a license renewal to be done for,

    • 5 RPA developer Robot but during renewal the quantity is decreased to 2. Now when tried to update your license in Orchestrator, then Orchestrator gets a conflict that out of 5 which two user retain the RPA developer license. Hence it throws error and admin has to manually deallocate the license from the Orchestrator UX and then try to update the license again.
    • Another scenario, when the license is renewed and some of the Robot or license type updated to new license type. for e.g. Studio license updated Studio Pro, RPA developer to Automation developer, non production to testing. In such situation as well, manually release the license consumed by user like Studio, RPA developer, non production and then update the license in Orchestrator UX and then reallocate the new license type (Studio pro, automation developer, testing) to users or Robot
    • If there are more quantity of such Robots then Swagger API or PowerShell script can also be used to update the Robot type or deallocate the license from the users/ Robot. Refer API References for details on swagger API.
    • Which type of API to call depends on the type to license which needs to be updated. API response needs to be tested before making mass changes. Hence it's advisable to reach out to UiPath Technical Support for assistance on it.