Troubleshooting Error "An Unexpected error occurred! (#100)" within Orchestrator

News Knowledge Base
1

How to resolve "An Unexpected error occurred! (#100)" error while navigating within Orchestrator?

Issue Description

Sometimes while navigating in Orchestrator you will see the error: An Unexpected error occurred! (#100)

720×233 13 KB

Root Cause

This error is thrown when scripts running on the client browser catch an undefined error from an HTTP request. For example, if logged into Orchestrator and the Orchestrator server responds with an HTTP 500 error, the error displayed in the browser will be “An unexpected error has occurred! (#100)”

Reproducing the Error

This error can be reproduced by causing Orchestrator to crash after logging into the site. For example, do the following:

  • Log in to Orchestrator
  • Modify the 'UiPath.Orchestrator.dll.config' (C:\Program Files (x86)\UiPath\Orchestrator) by adding an invalid key or anything that is not supported.
  • After saving the corrupted config, try interacting with the Orchestrator site.
  • If done fast enough, the error will be thrown.
  • If using this method, eventually the site will crash, and instead of displaying the Orchestrator site, it will just display a generic 500 error.


Diagnosing the Issue:

  1. When encountering reproducible issues, attempt to open the browser in developer mode to record HTTP calls. There's a likelihood of discovering a 500 error in the logs.

  2. Investigate the SQL server and identify the account being used for establishing a connection. Misconfiguration in the user's SQL account has been a common issue. If an AD-authenticated account is in use, potential AD problems may exist. Consider transitioning to a SQL authenticated account.

  3. Make sure to review the data in application event viewer logs on the Orchestrator machine.

  4. Aim to pinpoint the actual source of error.

    a. The SQL database is likely to be the culprit.

    b. Determine whether the website crashes entirely or not.

5. Check IIS logs and specifically the API call that is made when failing. Correlate the code and substatus code from here .

    • Navigate to IIS.
    • On the main machine level, double-click on IP Address and Domain Restrictions
    • Navigate to Edit Dynamic Restriction Settings.
    • Remove "Deny IP address based on the number of requests over a period of time" prompt.

image.png
image.png567×435 5.92 KB

6. If the issue persists, collect the following items after reproducing the issue and share them with UiPath Support for further investigation:

    • If you have any findings regarding points 1-5 addressed above
    • Application event viewer logs from the Orchestrator machine
    • A HAR trace from the browser
    • IIS logs from the Orchestrator machine ( %SystemDrive%\inetpub\logs\LogFiles )