Hey everyone,
Suddenly one of the servers used by my orchestrator bots has begun refusing connections from orchestrator.
Could not start executor. Rdp connection failed: Message: The server denied the connection., Last error: 65543
RemoteException wrapping System.Exception: Could not start executor. Rdp connection failed: Message: The server denied the connection., Last error: 65543
I can login to the server using the bot credentials and start processes through UiPath assistant and if I enable console login the connection is no longer refused, this however isn’t a solution as this seems to break other Ui automation steps of the process.
Does anyone have any idea what may be causing this? Only 1 server has been affected.
Hi @rhys.harwood Keep in mind that Orchestrator does not open conenctions to Robot Server. Robot service pings periodically to Orchestrator by a heartbeat mechanism and that way it receives instructions (for example to start jobs). It is the Robot Service the one that opens an RDP connection. Please check possible reasons for this error in Windows Server documentation:
Somehow adding the bot accounts directly to RDP users resolved the issue, even though the bots were already in a group that was allowed that access. Likely this wasn’t a UiPath issue.