Cannot Access Orchestrator Due To Error: An Error Has Occurred, Errorcode: 0

News Knowledge Base
1

How to access Orchestrator when prompted to the error " An Error Has Occurred, Errorcode: 0" ?

Sometimes certain malfunctions may require you to inspect Identity and IIS configurations. Following are steps you can traverse:

  1. Access Identity: Input "Orchestrator URL\identity" in the address bar and attempt to access it.

  2. Check Configurations in IIS: Verify if Identity, Orchestrator, and Webhooks are all functioning under the same username in IIS. If there's been any alteration in the Application Pools, like a user change, you should manually re-enter the user and password.

  3. Inspect App Status in IIS: Check if the Identity and Webhooks applications are actively running or have stopped in IIS (found under Application Pools). In case the apps are stopped, reset IIS and manually reboot the apps.

  4. Certificate Validity: Confirm if the IIS certificate is still within its valid period.

  5. Check Thumbprint in .json file: Cross-check the thumbprint in appsettings.Production.json. If it is different from the one in the certificate, replace it with the Thumbprint from the IIS certificate. Don't forget to save the file and then, restart IIS.

After these checks, if everything seems up and running but the problem persists, provide the following details for further investigation by the UiPath Support team:

  • UiPath.Orchestrator.dll.config file
  • Event Viewer Application logs (in .evtx format) from the Orchestrator and SQL servers.

This comprehensive analysis should be able to address the problem. If it persists, please contact technical support.

2

Thank You very much! the Thumbprint did the trick.