Troubleshooting Guide: 500 Internal Server Error / Server Error In '/' Application

News Knowledge Base
1

While browsing the Orchestrator website hosted in IIS it is showing 500 Internal Server Error.

Error Description: Sometimes, an Orchestrator Login might fail with a 500 error that might look like the following:

image.png


Troubleshooting Steps:

  1. View Detailed errors: Follow the below steps to find the root cause of the issue,
    1. Go to Windows -> Run -> Type in "Inetmgr"
    2. Expand Sites -> Select the Orchestrator website -> Right Click on it and click on "Explore"
    3. Now look for web.config file, and make the following changes as explained below
    4. Set the CustomErrors mode to = "Off" as shown in the screenshot below. (Make sure it's capital "O" and small "f")

  1. Set the httpErrors errorMode = "Detailed" as shown in the screenshot below


  1. Save the web.config file and Restart the Website from IIS
  2. Browse the page and a detailed error message shall be visible. One such error can be this:
image.png

  1. Assess the Application Event Logs:

Another excellent source to look for the potential root cause of the issue is the application event logs on the Orchestrator server. You should be able to see helpful errors and warnings arising from sources "Orchestrator", "IdentitySevice", "IIS AspNetCore Module V2", ".NETRuntime" that can give you more insight into the issue. Steps to collect the event logs are illustrated here:

How to get Application Logs from the Event Viewer.


Resolution for specific scenarios under consideration:

Based on the information obtained from the troubleshooting steps described above, the following steps may help to resolve the respective issue.

Issue 1:

​


Approach #1: Follow the below steps,

  1. Open IIS -> Orchestrator website -> Connection Strings


  1. Connection Strings (update the connection )



​

  1. Provide the server name , database name , username , password which is used to connect to the same database

​ ​

  1. Follow the same approach for both the connection string
  2. Restart the website from IIS
  3. This should fix the issue. Now launch the Orchestrator.

Approach #2: Verify the Application Pool details and reapply

  1. Navigate to
  • IIS -> Application Pool -> Advanced settings -> Identity -> Custom Account -> Set Credentials -> Provide Domain\Username & password.
  1. Recycling option of the Application Pool. Refer to below screenshot,

​

Approach #3 :

  1. IIS → Orchestrator website → Bindings → Select https bindings → Check SSL certificate → Select the appropriate certificate → Restart the website


Issue 2:

In case the following error is present: "Cannot add duplication collection entry of type "add"

The above error comes up due to multiple entries of "verbs" trying to be added, due to the following reasons.

Approach #1: Validate presence of multiple web.config files under Orchestrator installation folder. In this scenario, the duplicate web.config file must be removed accordingly.

Approach #2: Validate presence of a applicationhost.config file under Orchestrator installation folder, which has the same tags present in the web.config file. If yes, then remove the duplicate verbs from the applicationhost.config file.

Miscellaneous Issues:


A 500 error can occur due to a variety of other reasons. Refer to the following helpful articles and tackle the issue accordingly:


What next?


If the issue still persists, reach out to UiPath Support with the details collected in the troubleshooting steps and UiPath Product Support team will gladly assist further.