UiPath robots stopping execution and just hanging untill killed

Help
1

License type(Free, Trial/License code): Enterprise, unattended connected to Orchestrator

Studio/Robot version: 2019.4.4

Current behavior: robot stops at random step and hangs forever or untill killed from Orchestrator

A process running on an unattended robot (windows 10 vmware virtual) the process then stops at a random time, and does nothing untill i kill it from Orchestrator. no timeouts, no errorlogs, just nothing.
This has now happend more than 5 times in about 2 weeks.

The Windows log on the win10 machine has the following entries:
"UiPath.Service.Host 19.4.4.0
Subscribe hub failed, err : Connection started reconnecting before invocation result was received. "

“UiPath.Service.Host 19.4.4.0
SubmitHeartbeat: System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. —> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)
at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)
at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)
at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
— End of inner exception stack trace —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Service.Utils.OrchestratorHttpHandler.d__7.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Net.Http.HttpClient.d__58.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Service.Orchestrator.Clients.OrchestratorBaseClient.d__5.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Service.Orchestrator.Clients.OrchestratorBaseClient.d__4`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Service.Orchestrator.Clients.OrchestratorClient.d__17.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at UiPath.Service.Orchestrator.Notifications.HeartbeatGenerator.d__15.MoveNext()”

1 Like
2

Hi @dampergud1

Could you check with our technical support about this one?
It might be tricky to debug on the Forum, but I’m sure our support can offer some direct assistance :slight_smile:
Contact Technical Support

3

@dampergud1

Hi,

I am also experiencing the same problem where my Bots just completely hang even on simple tasks such as printing a log message. I have been advised by someone else who faced this issue to try version 2019.4.3 who he has said that it fixed all hanging issues! I suggest that you do the same and also Orchestrator (2019.4.2) works fine as well but it looks like a problem with StudioRobot versions: 2019.4.2 and 2019.4.4

4

I would only make one side remark - please make sure that the robot process and studio run on the same version. Version mismatch between the two will often lead to unexpected behaviours and instability.

1 Like