Orchestrator Throwing 500 Error When Application Running Under Customer Account

News Knowledge Base
1

Orchestrator throwing 500 error when application running under customer account.

  1. Check the application pools where application will be running under custom account

Uma.jpg

  1. In case server where the Orchestrator is installed and password is reset recently for the server
  2. It is mandatory to update the server password for the Identity, Orchestrator and webbook under application pool for the service account
  3. After replicating the above steps we can restart the IIS and we shall be able to access the Orchestrator application.