General Orchestrator Installation Troubleshooting

General FAQ for Orchestrator Installation issues.

This is a list of common things that can be checked when an Orchestrator install is failing. 

The Orchestrator installer also generates a log and that is usually the best thing to check first.


Getting the Log

 

1.       To understand the issue, the log needs to be captured.

a.       For MSI, re-run the installer from the command line and add the logging parameter

                                                               i.      i.e. UiPathOrchestrator.msi /l*vx log.txt

                                                             ii.      https://docs.uipath.com/orchestrator/docs/msi-command-line-parameters

b.       For platform installer:

                                                               i.      Go to %localappdata%\Temp in a file explorer.

                                                             ii.      There will be a file with the naming convention “XXXXXX_UiPathOrchestrator.msi, where the XXXX’s represent the date stamp.

2.       Open the log.

3.       Search the log. Common key words to look for are “Error”, “Failed” or “Exception”

4.       If the log message is not clear, send the log to UiPath so the support team can have a look. If desired, go through the items below as those are common issues we often see.

 


Things to Check:

1. Verify version of IIS and server roles and features prerequisite.
 
  • Go to IIS 'server' click on 'Help' from the menu tab
  • Click on 'About Internet Information Service' and you will get information on the IIS server
  • As recommended, the IIS version should be 7.5 and above to support the UiPath Orchestrator.
 
  • Verify the appropriate features are installed in the server using power shell
  • Open PowerShell with administrator privileges and run the command Get-WindowsFeature Web*
  • You can see all currently installed web roles and features as shown in the screenshot below
 
  • Click here to verify the roles and features returned
 


2. Verify URL IIS URL Rewrite module.
 
 
  • Go to 'Control Panel' and select 'Programs and Features' check that the 'IIS URL rewrite Module' is installed. 
  • If installed, skip this step. 
  • If not installed  click here to download and proceed with installation.
 


3. Verify the .NET version
 
  • Open 'command prompt' as administrator. 
  • Navigate to the default .NET installation folder.
  • cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319
  • Use the below command to check the version:
  • .\MSBuild.exe -version
 
  • If the appropriate .NET version is not available on the server as outlined in the Software Requirements for your version of Orchestrator, click here to download and install it.
 


4. Verify the Application pool identity user
 
 
Change the app pool identity to custom user if you are using the server in a domain. To change the application pool identity user, perform the below steps:
 
  • Open IIS manager or windows+r for the Run command window. Type inetmgr and enter
 
  • Click on 'Application Pools' à Select 'UiPath Orchestrator' à Click on 'Advance Settings' as shown in above screenshot
 
  • Click on the 'identity' and select the "..." as shown in the screen shot.
  • Select 'Custom Account' and click on set to provide the credentials as shown in the below screenshot


Note: If the username and password are not correct, the 'Application Pool' will not start and you will get a “503 server unavailable” error when you hit the Orchestrator URL


5. Verify SSL certificate validity.
 
  • Go to the IIS server à Click on 'Server Certificates' as shown in the below screenshot
 
 
  • You can check the certificate which you imported to the UiPath Orchestrator website and ensure the expiration date is acceptable.
  • If the certificate is expired, create a new domain or self-signed certificate and start installation
<img alt="" src="https://uipath-survey.secure.force.com/CaseView/servlet/rtaImage?eid=ka01Q0000019RsH&feoid=00N1Q00000Tffpw&refid=0EM1Q0000