Enabling Test-Suite (Test-Unattended Licenses) on Orchestrator Stand-Alone

Recently, we got our Non-Production licenses replaced with Test-Unattended licenses and applied to our Orchestrator Standalone on Azure. In order to support these licenses, we need to apply the Test licenses to machines by enabling -testAutomationFeatureEnabled via Powershell Script.

Upon running the following PS script in Windows ISE, we’re getting the error towards the end after 20 minutes of the script running.

.\Publish-Orchestrator.ps1 `

-action “Update” `

-unattended `

-package “.\UiPath.Orchestrator.Web.zip” `

-stopApplicationBeforePublish `

-azureSubscriptionId “00000000-00000-000-0000-000000000” `

-azureAccountTenantId “00000000-00000-000-0000-000000000” `

-azureAccountApplicationId “00000000-00000-000-0000-000000000” `

-azureAccountPassword “---------------------” `

-resourceGroupName “-----------------” `

-appServiceName “------------------” `

-testAutomationFeatureEnabled `

-verbose

(ERROR)
The script failed due to call depth overflow.
+ CategoryInfo : InvalidOperation: (0:Int32) , ParentContainsErrorRecordException
+ FullyQualifiedErrorId : CallDepthOverflow

Has anyone seen this issue before or know the solution? We are using Orchestrator 2022.4.1 (hosting in Azure)

Hello @david.sue!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff