Error "An error occurred while connecting to Orchestrator. Ensure that URL entered points to a valid Orchestrator instance." while installing/upgrading Action Center

News Knowledge Base
,
1

Why is the Action Center installer not accepting our Orchestrator URL?

Issue Description

Sometimes while running an Action Center installer to install or upgrade an Action Center instance, the following error may be encountered within the installer.

As a result of the above, expect to find a 1603 failure error code within the application logs in the Event Viewer on your Action Center server as shown below. (this code can be seen in the MSI installation logs as well.)

Resolution

  1. Begin by reviewing the Orchestrator-Action Center Compatibility Matrix. Action Center is compatible with only certain versions of Orchestrator.
  2. If this is a fresh installation, check if the supplied value for the Orchestrator URL within the installer is accurate. This should be the complete URL (i.e. including https://) and not just the Action Center hostname. Check Step 5 here for more details.
  3. Ensure that you have a valid certificate for both Orchestrator and Action Center at all times. This secure SSL certificate should have a "Subject" or "Subject Alternative Name (SAN)" that resolves to the DNS/hostname of your Orchestrator/Action Center instance respectively.
  4. In case of an upgrade, check if the "appsettings.json" file for the Action Center instance has the correct Orchestrator URL. You can find this file within the installation directory of the Action Center. The URL would be present under the "ServiceUrl" parameter in the file as highlighted below.

  1. The next step, in case of an upgrade, is to check the Registry values. URLs for Action Center are also encoded at the registry level. You can check the URLs (specifically the Orchestrator URL) under -- "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\UiPath\UiPath Action Center" as depicted below.

  1. If none of the above steps help, collect the following and share them with the UiPath Support team for further investigation:
  • An error screenshot along with the complete error stack trace
  • Installation/MSI logs produced by the installer
  • Application event logs from the Orchestrator and Action Center machines (if they are installed on separate servers) or just the Orchestrator machine (if they are installed on the same server)