Troubleshooting a 500.19 Error Encountered While Accessing the Orchestrator

How to resolve a 500.19 error encountered when accessing the Orchestrator?

Issue Description

Sometimes a 500.19 error may be encountered when trying to access the Orchestrator. See below for reference:

Troubleshooting Steps

The root cause of the issue varies. As such, you can follow a few different steps to troubleshoot and resolve this issue. Please find these steps below.

  1. ASP.NET Core Module
  • Start by checking the version of the ASP.NET Core IIS Module that is used for the Orchestrator installation. Make sure that it follows the prerequisites for the respective Orchestrator version that you are leveraging.
  • You can find more on this requirement here: Prerequisites for Installation - Orchestrator Server.
  • If the ASP.NET Core version seems correct, try repairing/reinstalling the same and check if it helps in alleviating the issue.

  1. Server Roles and Features

Verify if the following roles & features are installed/enabled on the Orchestrator Server: Server Roles And Features.

  1. Feature Delegation
  • Open IIS Manager (Start > Run > Type "inetmgr.exe") and click the connection to the local server in the tree view on the left side. Scroll down the feature list, find Feature Delegation, and double-click to open. See below for reference.

  • Click a feature (Error Pages) to see the delegation options in the task pane on the right and set it to "Read/Write". Read/Write means that the feature's corresponding configuration section is unlocked and can be configured in "web.config".

  1. Error-specific Troubleshooting

Review and follow the steps elaborated in the following articles, as suits best:

  1. Web.Config
  • Sometimes a 500.19 error may occur due to duplicate entries within the "web.config" file (C:\Program Files (x86)\UiPath\Orchestrator).
  • To resolve this, open the file, check for any duplicate sections, and get rid of the same. If you have a backup of this file, you may compare both for reference.
  • It is also a good idea to use an XML validator like this one to check for any potential syntactical issues in the file.

  1. ApplicationHost.Config
  • Navigate to "C:\Windows\System32\inetsrv\config\applicationHost.config" and edit the file.
  • Search for the setting: and modify it to "Allow" (ie: ).
  • Reset IIS and reload site.

  1. Assess Detailed Errors
  • If none of the above steps help, open the "web.config" file and enable detailed error logging by setting the: .
  • Reset IIS (Use command "iisreset" in CMD opened in Admin mode).
  • Browse for your Orchestrator again and reproduce the issue. This time, you should see more detailed errors in the Browser.
   
    
    
    
    
    
    
    
    
   
  • Apart from this, you should also assess the application event logs on the Orchestrator machine for further insight into the issue.
  • If the error information so obtained is useful, proceed to apply the relevant troubleshooting/resolution step.

  1. Next Steps

If further assistance is needed, collect the following and reach out to UiPath Support for further analysis:

  • Orchestrator environment details (Version, recent changes, infra, etc.)
  • Error screenshots
  • Summary of the troubleshooting steps performed until now
  • Application event logs from the Orchestrator machine after reproducing the issue along with a rough timestamp of when the issue occurs