Http Failure response for https://URL/odata/Settings/UiPath.Server.Configuration.OData.ActivateLicenseOffline(): 500 Internal Server Error

News Knowledge Base
,
1

When trying to update my license key using the Offline method I receive the error "Connection ID "XXXXXXXXXXXXX", Request ID "XXXXXXXXXXXXXXX": An unhandled exception was thrown by the application.System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list."

Issue Description:

Event Viewer error:

Connection ID "XXXXXX", Request ID "XXXXXX": An unhandled exception was thrown by the application.System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

The user encounters a "System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list." error message when trying to perform an offline update of the Orchestrator license key. This occurs when the numbers of runtimes allocated to Robots in Orchestrator (tenant> License tab) differ from the count on the new update license key.

This error can be prevalent when updating the Orchestrator license key offline. If your existing robots are consuming runtimes while performing the update, it can potentially result in a conflict if the available runtimes of your new license key do not match the currently consumed runtimes in Orchestrator.

Resolution:

The update issue was caused by the different number and runtime types existing on the active license key assigned to the orchestrator and the ones from the renewed license key.

Following these steps will resolve this issue:

  1. To begin the resolution, disconnect all Robots from the Orchestrator. By doing this, Orchestrator would have all the runtimes released and not being consumed by any Robot
  2. After ensuring that no Robot is connected, check the License tab. It should display that no Robots are consuming the runtimes
  3. Now, proceed with the License key update. Click the 'Update' button and follow the prompt steps to apply the update. It is crucial here to make sure that the License tab displays the correct number of runtimes as allocated in the new license key
  4. If the update is successful, see that the License tab will accurately reflect the runtime counts from the new license key
  5. Reconnect the Robots as needed, ensuring that the level of concurrency does not exceed the number of runtimes present for the corresponding type of Robot.

Note: It is important to manage and monitor the Robot runtime allocation especially when performing license updates to prevent such conflicts.