Troubleshooting A 500.30 Error In IIS Hosted UiPath Applications

News Knowledge Base
1

Why is a 500.30 error thrown despite a successful installation of the UiPath product?

Issue Description

While browsing for a UiPath application, for instance, the Orchestrator, a 500.30 error may be encountered:

Root Cause

Resolution

  1. Perform an IIS reset within the server where the product is installed. For this, launch the Command Prompt in admin mode and type "iisreset".
  2. Check the event logs on the application server (How to get Application Logs from the Event Viewer).
  3. If the issue is with an Orchestrator/Identity instance, check to see if the environment variable ASPNETCORE_ENVIRONMENT is defined. If its defined it should be set to 'Production' or deleted.
    1. Win + R to open a Run command.
    2. Enter 'SystemPropertiesAdvanced' and press the enter key.
    3. In the window that is opened, select 'Environment Variables'.
    4. Make sure that ASPNETCORE_ENVIRONMENT is not defined and if it is, it should be set to production.
    5. Take a screenshot and include that in a support ticket if one is raised.
  4. Look for errors from the source "IIS AspNetCore Module V2", and target accordingly. For example, the below error suggests an issue with the Identity Server certificate, eventually causing the 500.30 error when trying to launch the Orchestrator application in the browser. To resolve this, ensure that a valid SSL certificate is present in the Personal and Trusted Root folders within the Certificate Manager in the Orchestrator server that adheres to all the Identity Server prerequisites. The Orchestrator should be configured to leverage this certificate. For this, make any changes, as needed. (Changing The SSL Certificate For UiPath Orchestrator Website )

  1. If the issue is not fixed, open a ticket with UiPath Support, and include the Event Log messages in a .evtx format.