Licensing Generic FAQs

News Knowledge Base
1

What are the UiPath Licensing FAQs ?

  1. How to create a tenant?
In order to create the tenants, follow the instructions as described About the Tenant Context .
Post acquiring an Orchestrator license key, use this link for Activating your tenant license.
Also, refer to this link for Managing your licenses at the tenant level.
  1. Are separate license codes required for creating a tenant?
For creating a Tenant, follow the instructions Creating a Tenant. It is recommended to opt for either the Tenant Licensing Model, Host Licensing Model, or a mix of them.
  • If individual license is chosen for the Tenants, each one will need a separate license key
  • If the Host Licensing Model is chosen, the license key will be uploaded at the Host level and shared among the Tenants
  • If a mix of the Host Licensing Model and Tenant Licensing Model is required, a Host license + the number of licenses equal to the Tenants are needed to be individually licensed.
For details on how to manage the licenses, refer to the link About Licensing .
  1. How to add an extra Robot license to a tenant?
Post purchasing sufficient licenses and having received the confirmation by means of an invoice /mail, add the Robot license in the following two ways:
  • In case of host licensing regenerate and upload the License txt file, using the host license key. On seeing the updated number of licenses on the license page, redistribute the license from the host itself as explained Renewing or Updating Your License .
  • In the case of tenant-level licensing, please regenerate and upload the license txt file as explained Offline Activation using the tenant license key. Post this, you will be able to see the updated robot licenses on the license page of the tenant.
  1. How to move Robots from one tenant to another?
Post purchasing sufficient licenses, add the Robot license by following two ways:
  • In the case of host licensing, redistribute the license from the host itself as explained Orchestrator.
  • In the case of tenant-level licenses, provide the information in the following format to the sales and licensing support team:
  • Tenant key from which the Robots are to be removed
  • Tenant key to which the Robots are to be added
  • Number and type of Robots to be transferred
After receiving the updated keys, regenerate the license files for both tenants as explained Managing Your Licenses .
  1. How to switch from tenant-based licensing to host-based licensing?
To switch from Tenant to Host Licensing Model, open a ticket on UiPath Licensing support team from the Customer Portal and provide the details of the tenant license keys that you would like to merge.

Use host licensing by simply uploading a license file at the host level in Orchestrator version 2018.3 and above. Please note that at any point in time, a tenant can either take licenses from the host or from the license file uploaded on the license page of the tenant section. In order to allocate the Robots from the host, first remove the individual license for the given tenant.
  1. How to request a report for license usage?
UiPath can provide license usage reports only in the case of standalone licenses. For the Orchestrator, the monitoring can be done from the client’s end itself as explained License Usage .
To get the license usage report for standalone licenses, please submit a request to licensing and activation team along with the relevant license codes from the Customer Portal.
  1. How to request temporary licenses for upgrading to the latest version?
Provide the following details to the licensing support team by submitting a ticket from the Customer Portal :
  • Full name of the organization
  • Production license code
  • Number of days of temporary licenses
  • A short description of your upgrade and migration plan
Note: Forward this request to the concerned UiPath account manager and it will proceed based on his/her approval.
  1. What is the meaning of the 6003 error?
This error may occur because of a lack of connection between the robot machine and the UiPath activation portal. Please check the firewall settings of your machine or try the offline activation method as explained here.
  1. What is the meaning of the 4303 error?
This error may occur because of a lack of connection between the robot machine and the UiPath activation portal. Please check the firewall settings of your machine or try the offline activation method as explained here.
  1. How to get the pricing details of UiPath products?
Full details are available here.
  1. Error ‘Number of allowed activations exceeded’ thrown in trial version.
Trial codes are generated per company and not per individual. Any person from a given company and given country, who requests trials from our website receive the same code as any other person from the same country and company.
By default, UiPath shall give a trial for 10 individual users and if you are getting this error, this means that 10 unique users have already used this trial from your organization.

Provide UiPath with the below information so that your corresponding Account Manager can be approached for the additional activation:
  • Full name of your organization
  • Your work location
  • Short description of why you would like to have additional activation.
  1. "Number of allowed activations exceeded" error thrown in the Enterprise version.
Provide the following details to the UiPath Licensing Support team by submitting a ticket from the Customer Portal:
  • License Code
  • Product component that you are trying to activate (Studio/Robot/Orchestrator)
  1. Why is trial activation code not yet received in the welcome email?
If unable to view the license code in the email received from UiPath, open the email in a web browser. This should make the license code visible. If the situation persists, reach out to the UiPath Sales support team by contacting the Sales Team here.
  1. How to get an extension on my UiPath trial license?
Provide UiPath with the below information so that the corresponding internal account manager shall be approached for the additional trial request from you:
  • Full name of your organization
  • Department you work in
  • Your work location
  • License code
  • Why do you need a UiPath trial?
Provide the information here.
  1. How to request for trial code for a demo or POC?
Provide us with the below information, so that UiPath can process the additional trial for you from our internal account manager:
  • Full name of your organization
  • Department you work in
  • Your work location
  • Client name for whom you wish to perform this demo/PoC
  1. How to transfer a UiPath license from one device to another?
  • In case of a standalone license: Please provide the following details to the UiPath Licensing Support team by submitting a ticket here
  • License Code
  • Email Address of the user who is currently using the license
  • In the case of the orchestrator: If you want to license a new Robot, first you have to register it to Orchestrator as described here and the next step is to disconnect the Robot that is using the license and connect the new one to Orchestrator, for more details click here.
  1. How to shift from the trial to the Community version?
Community Edition is free of charge, UiPath does not provide support for it and it is designed for individuals, small companies etc.
Let the UiPath Licensing team know the reason a switch to Community Edition here and the UiPath Licensing team will be able to help you accordingly.
  1. How to extend the Community license?
If you represent a company, UiPath recommends to use the trial version of UiPath Enterprise Edition. Community Edition is free of charge, UiPath does not provide support for it and it is designed for individuals, small companies, etc.
Let us know the reason why you want to continue with Community Edition here and the UiPath Licensing team will be able to help accordingly.
  1. Why is my new trial code already expired?
A: Trial codes are generated per company and not per individual. Any person from a given company and given country, who requests trials from our website receive the same code as any other person from the same country and company.
By default, a trial code is valid for 60 days from the date of first activation. So, an expired trial code means that someone from your organization has already used that trial code.
Provide us here with the below information, so that UiPath can process the extension in trial for you from our internal account manager
  • Full name of your organization
  • Department you work in
  • Your work location
  • Why do you need a UiPath trial?
  1. Is a new license key for upgrading to the latest UiPath version?
In the case of standalone licenses, no new license key is needed for upgrading to the latest UiPath version. In case you are using an Orchestrator, some updates might be needed to the existing license key depending on which version you are currently using and which version you wish to update to. Please reach out to the sales support team by raising a ticket here.
  1. How to get an overview of the UiPath licensing model?
Find an overview of various licensing concepts here.
  1. How to get an extension on my ABBYY trial code?
Provide us the following information via a licensing support ticket here so that UiPath can process an extension in trial for you from your dedicated UiPath Account Manager:
  • Full name of your organization
  • Department you work in
  • Your work location
  • Why do you need an additional ABBYY trial?
  1. What is the meaning of ‘Activation failed with error -4212: Invalid License Number’?
Check the license code delivered to you and ensure to use the correct code. If the problem persists, provide us with the following information via a licensing support ticket here:
  • License Code
  • Invoice Number (If Available)
  • The product which you are trying to activate (Robot/Studio/Orchestrator)
  1. Why a ‘Standalone license activation error’ is thrown while activating ABBYY?
Install the product through the command prompt (silent activation). Re-install by following the steps mentioned in the instructions.
  1. Where to obtain installation instructions for ABBYY activation?
Note ABBYY Engine products work with the UiPath platform only if the licenses are procured from UiPath. Along with the license keys, UiPath always provides you the installation instructions. In case you need the instructions again, write to us via a licensing support ticket here.
  1. How to obtain ABBYY SDK license?
Provide us with the following information via a Licensing support ticket here:
  • Product: ABBYY Flexicapture Engine / FineReader Engine
  • Company Name
  • Email ID
UiPath will get back to you with an update soon, on the same ticket.
  1. How to obtain license UiPath Studio using a stand-alone key?

See here the steps to allocate a stand-alone license.

  1. How to Enable/disable the User License Management?

Root Cause: If the User License Management is enabled, there is one setting in Orchestrator that is greyed out and cannot be changed - Tenant > Settings > Robot Security > Unattended Robot authentication type. This cannot be changed to Hybrid unless the User License Management option is disabled at the Automation Cloud level.

Resolution:

  • Navigate to Admin -> Settings -> Advanced

  1. How to resolve the error observed while creating the first ML Skill in AI Center Cloud - Insufficient license resources for tenant Id *********** ?

An error is generated while creating the first ML Skill in AI Center Cloud - Insufficient license resources for tenant Id ***********, if the AI-Robot license is not allocated to the tenant.

Follow the below steps:

  1. Go to the "Edit Services" for the specific tenant in the tenant's tab:

  1. Then update the license for AI Robot from zero to at least one in order to create a skill. Refer to below screenshot:

  1. Now try to create the skill and it should work.

If it still does not work, it indicates that the AI Robot license is already occupied with some ML skills or pipelines. Free up some licenses and then try to create ML skills.

  1. How to get rid of the "You have more licenses allocated to your services than you have available to your organization.." message from Automation Cloud?

Follow the below steps to remove the error message:

  1. Log in to Automation Cloud and navigate to the "Admin-->Licenses" page
  2. Select the "Robots & Services" tab and take note of available runtimes (Attended, Unattended, Testing, etc.)
  3. Navigate to the "Admin-->Tenants" page and identify the tenant that is using the runtimes from step #2
  4. Click the second icon from the right for that tenant. It looks like below

1.png

  1. Decrease the number of runtimes to match the count in step #2 and click the "Save" button
  2. Re-load the page to see the "You have more licenses allocated...." message disappear.

Note: This affects Orchestrator if all the runtimes (Attended, Unattended, Testing, etc.,) are used. Hence, double-check to make sure it's okay to remove the runtimes or check with the Sales team to purchase more runtimes.

  1. No More RPA Developer/ Attended/ Development Robots Available. Please Update Your License! (#1900)

Issue Description: While trying to reset a password of one of our Orchestrators Users (a common user).

When the button UPDATE is clicked, one error message comes up on the screen informing that no more development Robots available. please update your license (#1900)

Background Check: Looking at licenses, 1 license for "RPA Developer - Named User" is present.

    2.jpg

    Resolution:

    1. Check if the Automation Cloud subscription is expired. If yes, reach out to us on this portal or the UiPath Sales representative to renew the same.

    1. Check if there are available Licenses for the User/Robot in the Tenant -> License section of Orchestrator service.

    1. If the runtime information is not sufficient or is not visible, navigate to the Automation Cloud platform and check if the affected License type is assigned to the service or not. If not, allocate a License.
    2. In the case of the Modern folder, check if the User is mapped to the Folder. If not, please assign the User to the Folder.
    3. Navigate to Orchestrator service -> Tenant -> Folder -> Click on Folder -> Check/Add User
    4. Check the available purchased License and update the License type accordingly in Robot settings.
    5. Navigate to Tenant -> Manage Users/Users -> Click More Actions -> Robot setup -> Updated License type.

    Read More on:

    1. User not getting the license allocated that was configured to the AD group. This issue usually affects a subset (1+) users but the rest of them are working as expected.
    Root Cause: The user signed in and created an account before the group was allocated licenses. In this situation, the user is created without the appropriate licenses configured. This is usually a problem when users are configured through AD groups.
    Resolution:
    1. Delete the configured user from Orchestrator (Manage Access -> Find User -> Delete)
    2. Have the affected user log into Orchestrator again so their profile is configured using the AD group settings.
    1. Post a license extension, the following message is returned when trying to update the license in Orchestrator: " Activation failed! There are no more allowed activations on this license code."

    Issue Description: Following a license extension, the user should update the license in Orchestrator. However, some might mistake this with an activation, case in which the following message appears:


    Root Cause: This error appears when the user is logged in to the Host tenant and tries to activate the license instead of updating it.

    Resolution:

    1. Click on "Update" rather than "Activate".
    2. Alternatively, they can click on "Deactivate" and then "Activate".
    1. Licensing Model Data Missing During License Activation of Studio.
    The activation request reflects a mismatch in the license details.
    • Make sure the right license code is used for activation if a standalone license key is present
    or
    1. Orchestrator license is not able to be offline activated, the error " Invalid license format, could not validate signature" for 2020.10.2 Version.

    Remove the below lines

    from UiPath.Orchestrator.dll.config file and iisreset.

    1. How to handle when it is not possible to start the Studio application and cannot activate the Studio through the license of the Cloud Orchestrator?

    1. Go to Cloud instance -> Orchestrator -> tenant (not folder) and open the settings tab
    2. From settings go to the security tab and disable: Enforce user authentication, disable Robot key authentication
    3. Disconnect the Robot and reconnect.

    image.png

    1. Users do not have access to the dashboards in Cloud Insights

    Resolution: For Insights Cloud

    1. Click on 3 dots

    1.png

    1. Then click on edit on the necessary user and provide them "Designer" access

    2.png

    Note: Even though users might have Admin rights, a Designer role is required in order to have access to the dashboard.

    1. Update Failed: Please Disconnect Some Machines To Match The Number Of Defined Licenses (#1905)
    Error:
    Root Cause:
    This error occurs when the runtimes on the license have been updated (especially when removed) from UiPaths side and when the customer updates the license in Orchestrator.

    Example - A customer has 10 Unattended runtimes on a license expiring. With the renewal, the customer decided to have 9 Unattended runtimes and 1 Studio runtime. Based on this requirement, UiPath updates the runtimes on the same license code.
    The Orchestrator instance of the customer already has 10 Unattended robots provisioned and when the customer tries to update the license from Orchestrator, the above error occurs as there are 10 Unattended runtimes allocated instead of 9.


    Resolution: Below methods can be used to resolve the issue

    Method 1:

    1. Remove the existing license by clicking the REMOVE button
    2. Click ACTIVATE ONLINE button and provide the license code again

    Method 2:

    1. Remove Unattended Robot from the Robots page
    2. Click the UPDATE button from the License page. This logic applies to all runtimes and not just Unattended.
    1. A local license is required message is displayed in the Robot tray when connecting to Orchestrator.
    This error usually comes up if the Robot is created in Orchestrator with a "Stand-alone license"/"external license" field selected as a part of the Robot entry. Validate this by opening the respective Robot entry in Orchestrator via the edit option, and this check box should be at the bottom of the edit pop-up (see below screenshot) . If it is checked, try removing the option and attempting to run the job to validate if the behavior still exists.
    1.png
    If the above option is checked, then Studio/ Robot is looking for a Stand-alone license and not an Orchestrator license. Read more on the Connecting To Orchestrator.
    1. How to troubleshoot Robot Licensing Failure when there are no available runtime licenses?

    The Robot Licensing failure error occurs, when the number of Robots provisioned in Orchestrator are more than the available runtime licenses.
    In such a scenario when Orchestrator tries to allocate the license to Robots which are not licensed yet and there is no available runtime license to allocate, It generates this message in the event viewer.

    For Example: Considering the below scenario (For first machine - All runtime has been used up, For second - 1 Runtime License is still available)

    The runtime allocated to Machine 001 is 1 thus at a given time only One Robot User account will be able to process & any other process gets triggered on the same Machine will go into pending state as already 1 Runtime license is being used by the Robot and for the second Robot user account there is no available Runtime license at that given time.
    In this scenario, the error message will be logged in the event viewer.

    ​


    Now for the Second Machine 002, the available Runtime is 3 where the current user is 2 at that particular time.
    At any given time you can run 3 processes simultaneously on the same Machine for 3 different user account which is provisioned.
    In this scenario, no error message will be logged in the event viewer.

    Note: Provisioning of 200 Robots will require 200 Runtime licenses, to execute all bots at the given time.

    Version: >= 2018.3.x

    1. Can tenant licenses be allocated from the Host via API?

    Yes, Host licenses can be allocated via API. One can do a POST call to HostLicenses group's SetTenantLicense to allocate the specific number of licenses to a particular tenant.

    Note that this is only possible by the host level user. More information regarding this call can be found from the Swagger UI for Orchestrator.

    The number of licenses can be passed along with the TenantID in the body of the API call, to allocate the respective number of licenses to the respective tenant, as shown below.

    1. How to delete the host tenant license using the API key?

    In order to delete the host tenant license, use the below API key

    Steps to follow
    1. On the UiPath Orchestrator database, run the below query [Recommended to take help of DBA team]. It shall provide the ID which needs to be passed to the API to perform the deletion.
    • Note: Replace the Database_name with the actual database in use
    SELECT ID FROM [Database_name].[dbo].[HostLicenses] where IsDeleted = 0
    1. Open Orchestrator website and logon with host tenant
    • Note: Use local user instead of Windows authentication.
    1. Open another tab in the browser and open swagger using the link shared below
    • Note: Hostname needs to be replaced with the hostname used in the Orchestrator URL
    https://hostname/swagger/ui/index#!
    1. Once Swagger opens up, go to Delete License API under "Host License " Section
    2. Provide the value of ID ( Information received in Step 1) and hit "Try it Out"

    Note: This feature is applicable starting from 2018.3.X version of UiPath Orchestrator.

    1. Robot Status Connected Unlicensed In Classic Folder
    Note: All the approaches mentioned below are valid for Classic folders only.
    Method #1: Incorrect user defined in the Orchestrator. Define the same user while provisioning the Robot section in Orchestrator with which it is logged in to the Robot / Studio machine.
    1. To validate open the command prompt in the Robot/Studio and check the user using the command "whoami"
    2.jfif
    1. Open the Orchestrator and check the Robot Page to validate the user defined. It should match the username received in Step 1 command.
    1.jfif
    Method #2: User currently logged in does not have a Robot created on Orchestrator.
    Make sure that the current user logged into the robot machine is the same as the user under which the robot is provisioned in Orchestrator. If these do not match, you will see the robot as unlicensed. To resolve, either
    • Log in with the same user that you see under the "Domain\Username" field in the Robot settings on Orchestrator
    ( or)
    • Provision a new robot in Orchestrator with for the current user.
    Method #3: Insufficient number of licenses.
    If using concurrent licenses, make sure that other users/robots are not consuming all available licenses. Concurrent licenses are consumed when:
    • The Robot is connected to Orchestrator
    • The UiPath Robot Tray or Agent Desktop is running (and not only while it is executing a process)
    • Studio is running
    Take a look at About Licensing for more information.
    Method #4: In case of using Cloud Platform, there might be a license propagation issue.
    Possible scenarios:
    • Product numbers are not the expected ones
    • License expires earlier
    • License has wrong subscription and so on
    • Downgrade to Trial from Community or any other license service change
    In this sort of situation, UiPath Support should gather all the licensing information from Boon, Automation Cloud and Orchestrator, like “Support ID” and general licensing page details.
    Need to compare them and see if the issue is between Boon and Automation Cloud or between Automation Cloud and Orchestrator. This will help to speed up the investigation & resolution process.

    Method #5: If these five criteria are met:
    1. Robot Status: Connected, Unlicensed
    2. Hovering mouse over UiPath Assistant Status icon yields: 'There are no available licenses on the server.'
    3. NonProduction Robot license is being used.
    4. Machine Type is Standard.
    5. The following exceptions are written to the Windows Event Viewer Application Log when the NonProduction Robot attempts to connect to the Standard Machine in Orchestrator:
      • UiPath.Orchestrator.Core.Exceptions.LicensingException: Error code - 1913, Message - 'There are no available licenses on the server.'
      • UiPath.Service.Orchestrator.Core.NoUserSessionException: There are no available licenses on the server. ---> [Http Status 409][Orchestrator Error Code 1913]UiPath.Service.Orchestrator.Clients.OrchestratorHttpException: There are no available licenses on the server.
    Take the following corrective action:
    1. Remove Some Development Robots To Match The Number Of Defined Licenses 1908

    Error Message: When trying to update the license, the error message is appearing:

    • "Please remove some Development Robots to match the number of defined licenses. (#1908) "

    Resolution:

    1. When this is error is occurring in the license tab while updating the license, check what Studio licenses are available on the new license and how many are active in the current system (by clicking on the See more under the respective license).
    2. Then remove* the studio/studio pro licenses from the users/Robots and then update the license
    3. Add the licenses back to the users, based on the licenses received.

    Workaround: Do not allow to remove all the licenses, the check box for Stand Alone license on the user/Robot can be added and Orchestrator will not take in consideration as a license consumed.

    1. Enable Test Automation Module To View Studio Pro License for Orchestrator 2020.4 and below.

    Studio version 2020.4.1 introduces the new Studio Pro license which unlocks access to the whole Test Suite capabilities. Refer to the release notes Release Notes - Studio 2020.4.1

    To Enable Test Auto: It is required to enable test automation to see the StudioPro license in the Orchestrator. Follow the below steps based on the type of installation,

    • If installation is using .msi/.exe on-prem,
    1. On Orchestrator web application server navigate to Control panel -> programs and select the Orchestrator.
    2. Click on Change
    3. Select the ‘Test Automation’
    4. Follow the steps shown on the popup

    See here for more information: Test Manager Installation

    • If Orchestrator is deployed in Azure PaaS, in order to enable test automation do the following:
    1. If Orchestrator is already deployed without enabling the Test Automation module, configure the following settings for your App Service before running the Publish-Orchestrator.ps1 script:
      • AppSettings: Key=TestAutomation.ModuleEnabled - Set to True to enable the Test Automation module.
      • AppSettings: Key=TestAutomation.FeatureEnabledByDefault - Set to True to enable the Test Automation module by default.
    2. To set a database connection string for the Test Automation module, follow the steps described for the -testAutomationFeatureEnabled parameter in Publish-Orchestrator.ps1 parameters.
    3. After that, run in PowerShell the Publish-Orchestrator.ps1 script with the same parameters as for an upgrade but adding the -testAutomationFeatureEnabled parameter:
      • -appSettings @{"TestAutomation.ModuleEnabled"="true"; "TestAutomation.FeatureEnabledByDefault"="true"} ?
    4. Once enabled, then log in to TM with the Admin account on the tenant where the tenant admin is.

    Note: Starting with 21.8 Studio Pro profile is retired but all the functionalities that were exclusive to the Pro version are now available in Studio. Test manager can still be used in the newer versions

    1. How to use the Automation Express license for an On-Premise installation of Studio?

    The Automation Express license type grants access to StudioX and Studio Web.

    In an On-Premise setup, after signing in to Studio or Assistant in order to acquire the license, if using an older version of Studio (22.4 or lower), the application will close without any warning or error messages.

    Since the Automation Express license type was not available when Studio 22.4 was released, the product was not interpreting the new license type and it crashed after Sign in.

    Root Cause: Since the Automation Express license type was not available when Studio 22.4 was released, the product was not interpreting the new license type and it crashed after Sign in.

    Resolution:

    • Download and install a newer version of Studio (22.10+) and Sign in again.
    • The license should be acquired from Orchestrator and the StudioX profile will be loaded.
    Refer to below for more information,
    1. Unable To Configure Attended Robots Despite Allocating Attended Licenses

    Resolution: Follow the below steps to connect the Attended Robot:

    1. Go to Tenant > Machines > Create the Template and provision the machine
    2. After provisioning the machine template, create a Floating Robot
    3. Go to Default Folder > Robots > Add a new floating Robot
    4. Now connect floating Robot to an environment
    5. Go to environment > If environment already exists then add the floating Robot to that environment or create and assign a new environment for the defined floating Robot
    6. Go back to Machines and copy the machine key for the floating machine created
    7. Connect with your UiPath Assistant.

    Addition to above:

    1. Create a floating machine template
    2. Only modern folders are available and the setting should be disabled to add the classic folders
    3. Enable the settings to activate the classic folders
    4. Add a new classic folder
    5. And then the provided steps in the above is good and follow the same to create an Attended Robot.
    Note: Cannot allocate the Attended license Robot in the Machine template.
    1. Process Mining Update License Code
    • If a new license code is present(i.e. actually a different code),
      • then deactivate the current code first using the 'deactivate' option and then it will allow to enter the new code.
    • If existing license needs to be extended (given a new end-date),
      • press "Update" button .


    1. Error "Unable To Retrieve A License. Please Contact Your IT Department" Thrown While Licensing Unattended Robot

    Error Description: The following error is encountered while licensing an Unattended Robot,

    • "Unable to retrieve a license (please contact your IT department)"
    Root Cause: For On-Premises Orchestrator (v2022.4 and above), this issue is observed when Robot Authentication (Tenant > Settings > Robot Security) is set as follows,
    • Unattended Robot Authentication : Hybrid / Client Credentials
    • Attended Robot (User) Authentication : Interactive Sign-in SSO.

    For Automation Cloud Orchestrator, the following is observed for scenarios:

    1. User License Management is disabled. Robot Authentication (Tenant > Settings > Robot Security) is set as follows:
      • Unattended Robot Authentication : Hybrid / Client Credentials.
      • Attended Robot (User) Authentication : Interactive Sign-in SSO.
    2. User License Management is enabled in Automation Cloud (Automation Cloud > Admin > Organization Settings > User License Management option enabled). In this scenario, Interactive Sign-In SSO is enforced for Attended Robot (user) authentication.

    This observed behavior while licensing Unattended Robot i.e. the message "Connected to Orchestrator. Unable to retrieve a license (please contact your IT department)" is the expected behavior due to the Robot Authentication settings for Attended Robot ("Interactive Sign-in SSO"). An Unattended Robot is deployed in service mode and works without human supervision.

    Since a user has manually logged into the Robot machine, the scenario is an Attended scenario despite the license being unattended. If the Robot Authentication for Attended Robot in Orchestrator Settings is set to 'Interactive Sign-in SSO.', a sign-in is required.

    Resolution:

    In case the Robot Status is required to be 'Connected, Licensed', then one of the following steps can be done:

    1. Use interactive sign in i.e. Open UiPath Assistant > Preferences > Orchestrator Settings > Click on 'Sign In' > Sign into Orchestrator.
    2. Update the Robot Authentication method for the Attended Robot to 'Hybrid' : Login to Orchestrator > Tenant > Settings > Robot Security > Robot Authentication > Select the Radio button for 'Hybrid' for the Attended Robot (user) authentication and click on Save. Once this is done, the Robot status in UiPath Assistant will be 'Connected, Licensed'.

    For Automation Cloud, if User License Management is enabled, then Interactive Sign-In SSO for Attended robot authentication is enforced. Hence, a sign-in would be required to get the Robot Status as "Connected, Licensed".

    Read more on the Attended vs Unattended Robots .

    1. Connected, Unlicensed: ''You Are Not Authorized To Perform This Action"

    Issue Description: Status on UiPath Assistant is Connected, Unlicensed and says: "You are not authorized to perform this action" .

    Screenshot:


    Root Cause: This message is encountered when connected with the machine key of one tenant, but signed in to another tenant.


    Resolution: Sign out from the Assistant and the status should be licensed in case of service mode.

    For Attended Robots (Attended, Studio, etc) it is recommended that Robot should be in user mode and sign in via Service_URL.

    1. Why is editing restricted in Studio when using a Standalone Attended Robot license?

    In cases where the license has been purchased for Attended Robot Named user, the Studio license is just available for read-only purposes.

    1. Option For 'Sign-in' And 'Connect to Orchestrator' Disabled (Greyed Out) On UiPath Studio Licensing Screen

    Issue Description: After Studio installation, when Studio is opened for the first time, the licensing screen has only the 'Standalone options' method enabled and the other methods i.e. 'Sign in' and 'Connect to Orchestrator' are disabled.

    The above scenario is observed when the Robot is deployed in Service-mode (option "Register UiPath Robot as a Windows Service' was selected during installation or the Robot was installed in Unattended mode and the Studio installation option was checked) and the logged-in user is not an administrator on the respective machine.


    Root Cause: The Robot is deployed in Service-mode (option "Register UiPath Robot as a Windows Service' is selected during installation or the Robot is installed in Unattended mode and the Studio installation option was checked) and the logged-in user is not an administrator on the respective machine.

    Resolution: Perform either of the following,

    • Start UiPath Assistant/Studio as an administrator to modify these settings
    Or
    • Install the Robot in User Mode. This can be done as follows,
    1. Add or Remove Programs >
    2. Click on UiPath Studio and click on change/modify >
    3. Uncheck the option "Register UiPath Robot as a Windows Service"
    4. This step can also be performed using the installer file.
    1. Robot Showing Connected Unlicensed In Cloud Orchestrator

    If the Robot was shown connected in the Cloud Orchestrator and connected unlicensed in the UiPath assistant.

    1. Disable "User License Management" in Organizational settings(Admin->Organizational settings ).
    2. Navigate to Tenant->Settings->Robot Security
    3. Select "Hybrid" under "Attended (Robot) Authentication". Ensure the "Hybrid " option should be selected for both Attended and Unattended
    4. Click Save

    1. After making the changes under Robot security the Robot status automatically changes to connected licenses.


    54. “Activation failed! There are no more allowed activations on this license code. If you believe this is a mistake contact us here”
    - this error message appears mainly when trying to use Standalone Automation Developer Named User License
    There could be 2 root causes when this error is generated:
    1. The customer is trying to use the license which is already active under a different user (validate the user account under which the activation is failing and make sure that there are enough activations available for the customer to use)
    - if the customer requires additional activations please refer him to the account owner and advise him to open a new ticket with the Licensing/Sales Ops team
    2. The license key used is expired
    - check the license key validity in BooN, in case it is expired check if there are other/new licenses that the customer can use and also refer him to the Account Owner for further instructions