Platform Configuration Tool Failing Pre-Check On Primary and Secondary Nodes For Upgrade From 2019.10 To 2021.10

Why does On-Premise Orchestrator upgrade from 2019.10 to 2021.10 fail on pre-check?

Issue Description: For Upgrade From 2019.10 to 2021.10, the Primary Node The Pre-Installation Check fails the SSL Check for the following error -"Orchestrator IIS binding host name and Identity Server Orchestrator URL are different."

On Secondary Node - The Pre-Installation Check fails due to the following error -"Orchestrator is not installed. Can not perform the rest of platform pre-installation checks."

This is the PS command being executed:

  • .\Platform.Configuration.Tool.ps1 -Readiness -InstallationDirectory D:\Uipath\Orchestrator\ -verbose.
Orchestrator is definitely installed in this directory.


Resolution: Reference on multi-node installations - Upgrading and Migrating. On a Test installation in preparation for updating Prod environment,

  1. Run command prompt as SQL account user based on DB user being an AD account, rather than SQL user
  2. Run installer from c:\temp folder using modified string, granting admin permission
  3. Correct DB name from UiPathdbt to UiPathTest per DBA (if db is not encrypted, the APP_ENCRYPTION_KEY parameter is not needed).
  4. Remove "TransparentNetworkIPResolution = FALSE" from SQL connection parameter in web.config

** Upgrade to Orchestrator 2022.10 is completed.

If using SECONDARY_NODE=1 PARAMETERS_FILE=c:\temp\upgradeParams.json command line parameters to upgrade secondary nodes and error thrown is,

  • MSI (s) (EC!C0) [12:47:55:211]: Closing MSIHANDLE (41) of type 790541 for thread 6592
  • CheckWindowsFeatures error: The following windows features are missing from this machine: IIS-ApplicationInit
  • MSI (s) (EC:6C) [12:47:55:258]: Closing MSIHANDLE (37) of type 790542 for thread 8348
  • CustomAction ValidateEnvironment returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
  • Action ended 12:47:55: ValidateEnvironment. Return value 3.

This should be correctable by installing the Application initialization feature as part of IIS, per IIS 8.0 Application Initialization - Prerequisites .