Orchestrator thrown Websocket exception

Hi

When the bot was running from orchestrator, the orchestrator thrown a web-socket exception followed by timeout exception and followed by Robot does not exists Exception. Though, the state of Robot was “Running” in orchestrator jobs, there is no progress in the process and got stuck.

Kindly help me with this Issue and why and when does it occur?

Thanks,
Santhosh

2 Likes

Hi @SanthoshKumar876,

I have similiar issue long before on v 2016, everytime the issue occurred, a different root cause was identified.

  1. Connection between bot machine and orch was lost
  2. out of memory exception - in this case process was seen running on orch ,but on bot machine there was a UiPath robot error “out of memory exception”.

Thank You,
Shubham Pratap

Hi @Shubh1801

I am using v2019. at what other circumstances,the connection will be lost between bot machine and orch except change in profile credentials.

Thanks,
Santhosh

1 Like

Hi

This is the exception I have got in the orchestrator.

Error while closing the websocket: System.Net.WebSockets.WebSocketException (0x80004005):
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host

Thanks,
Santhosh

1 Like

Hi @SanthoshKumar876,

Check this once:

1 Like