UiPath Orchestrator - Process is not running successfully,Exception is thrown!

Process is not running when we connect Robot via Services and Packages download also wasn’t successful and when we run the process as an agent after having killed the services,Process was not running due to some permission issue and Packages download was successful.

Then,we got some exceptions when we run the process as an agent after having connected with Orchestrator such as “Job_Debit_Credit_Stopped(forced)!” and “Job stopped by Orchestrator”.

Then,we got some exceptions when we run the process through Services after having connected with Orchestrator ,such as
“This request operation sent to net.pipe://localhost/UiPath/service/executor did not receive a reply within the configured timeout (00:20:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.\r\n\r\nAn ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:\nSystem.Exception: This request operation sent to net.pipe://localhost/UiPath/service/executor did not receive a reply within the configured timeout (00:20:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.\n”

What could be the solution for this kind of issues? Please advise.

1 Like

push the topic. I have the same issue. Robot is connected remote, works perfectly. Machine is available.

i tried a restart , and a robot reconnect. Nothing helps.

Hi @berndp3

What is Orchestrator version?

any update on the issue. version in use: 2018.4.5

It might be related to this issue with this fix:

Could you try and let us know?