During one of the automation jobs we are frequently seeing the below errors from UIPATH Orchestrator.
Execution error : System.Exception: An existing connection was forcibly closed by the remote host
Can someone tell us why is this error happening and what can be done to prevent or monitor the same?
An existing connection was forcibly closed by the remote host Ooops! We’re sorry! It seems Orchestrator is down. Some of the possible causes are:
The server was restarted from Internet Information Services (IIS)
The server was shut down
A clumsy new colleague unplugged your server
This is a list of errors that usually occur in Orchestrator and cause the Robot to not start a job. These errors can be found in the Jobs page, in the Job Details window.
No robot available for user X
This error is displayed when the Robot provisioned on Orchestrator has a username does not coincide with the Robot machine’s username.
Permission missing: Launcher
This error is received in the following scenario:
robot is connected to orchestrator with user “abc”
on the robot machine you try…
Can this be a reason where the machine which is running the automation got disconnected from the Orchestrator for a brief period of time when it is trying to fetch a workflow file or updating an asset or fetching from a queue?
Can this be proactively monitored?