Jobs triggered from Orchestrator fail to start with the error above. If I manually open an RDP session on the VM and keep it active, the job runs fine. The error only happens when there’s no active session on the machine — i.e., when the robot tries to start its own RDP connection from a logged-off state.
Network connectivity to the VM is confirmed working, and the process runs correctly whenever a session is already open manually.
Could anyone help me with this?
This is the error:
Robot.ExecutorFailedStart - Could not start executor. Please ensure the user is allowed to access the computer via Remote Desktop. Original message: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085
—> System.Security.Authentication.AuthenticationException: Please ensure the user is allowed to access the computer via Remote Desktop. Original message: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085
{“Code”:“Robot.ExecutorFailedStart”,“Title”:“Could not start executor. Please ensure the user is allowed to access the computer via Remote Desktop. Original message: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085”,“Detail”:“System.Exception: Could not start executor. Please ensure the user is allowed to access the computer via Remote Desktop. Original message: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085\r\n —> System.Security.Authentication.AuthenticationException: Please ensure the user is allowed to access the computer via Remote Desktop. Original message: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085\r\n —> System.Runtime.InteropServices.COMException: Rdp connection failed: Message: The connection transport layer failed. Last error: 131085\r\n at UiPath.Rdp.NativeInterface.RdpLogon(ConnectOptions rdpOptions, String& releaseObjectName)\r\n at UiPath.Rdp.FreeRdpClient.<>c__DisplayClass7_0.b__1()\r\n at System.Threading.Tasks.Task1.InnerInvoke()\r\n at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)\r\n--- End of stack trace from previous location ---\r\n at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)\r\n at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)\r\n--- End of stack trace from previous location ---\r\n at UiPath.Rdp.FreeRdpClient.Connect(RdpConnectionSettings connectionSettings)\r\n at UiPath.Session.Internals.WtsApi.ConnectRdp(RdpConnectionSettings connectionSettings, CancellationToken ct)\r\n --- End of inner exception stack trace ---\r\n at UiPath.Session.Internals.WtsApi.ConnectRdp(RdpConnectionSettings connectionSettings, CancellationToken ct)\r\n at UiPath.Session.Internals.WtsApiExtension.ConnectRdp(SessionOptions sessionOptions, CancellationToken ct)\r\n at UiPath.Session.Internals.WtsApiExtension.ConnectRdp(SessionOptions sessionOptions, CancellationToken ct)\r\n at UiPath.Session.SessionHandler.<ConnectRdp>g__ConnectRdp|12_0(CancellationToken ct)\r\n at UiPath.Session.SessionHandler.ThrowIfLegalNoticeEnabledWhileConnecting(Func2 connectFunc, CancellationToken ct)\r\n at UiPath.Session.SessionHandler.ConnectRdp(CancellationToken ct)\r\n at UiPath.Session.SessionMonitoringService.<>c__DisplayClass7_0.<g__Connect|8>d.MoveNext()\r\n— End of stack trace from previous location —\r\n at UiPath.Session.SessionMonitoringService.<>c__DisplayClass7_0.<g__ConnectWithRetry|1>d.MoveNext()\r\n— End of stack trace from previous location —\r\n at UiPath.Session.SessionMonitoringService.RunMonitored(SessionOptions sessionOptions, CancellationToken startCancellationToken)\r\n at UiPath.Session.Internals.SessionFactory.GetSession(SessionOptions sessionOptions, CancellationToken startCancellationToken)\r\n at UiPath.Session.SessionProcessLauncher.<>c__DisplayClass11_0.<g__WithTimeoutMessage|2>d1.MoveNext()\r\n--- End of stack trace from previous location ---\r\n at UiPath.Session.SessionProcessLauncher.<>c__DisplayClass11_0.<<StartProcessInMonitoredSession>g__Run|1>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n at UiPath.Session.SessionProcessLauncher.<>c__DisplayClass11_0.<<StartProcessInMonitoredSession>g__RunGuarded|0>d.MoveNext()\r\n--- End of stack trace from previous location ---\r\n at UiPath.Service.Impl.UnattendedProcessStartHelperCsharp.StartUsingSessionLibraryCsharp(String executable, String arguments, CancellationToken ct)\r\n at UiPath.Service.Impl.UnattendedProcessStartHelperCsharp.Start(String executable, String arguments, CancellationToken ct)\r\n at UiPath.Service.Impl.ExecutorProxy.Start()\r\n --- End of inner exception stack trace ---\r\n at UiPath.Rdp.NativeInterface.RdpLogon(ConnectOptions rdpOptions, String& releaseObjectName)\r\n at UiPath.Rdp.FreeRdpClient.<>c__DisplayClass7_0.<Connect>b__1()\r\n at System.Threading.Tasks.Task1.InnerInvoke()\r\n at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)\r\n— End of stack trace from previous location —\r\n at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)\r\n at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)\r\n— End of stack trace from previous location —\r\n at UiPath.Rdp.FreeRdpClient.Connect(RdpConnectionSettings connectionSettings)\r\n at UiPath.Session.Internals.WtsApi.ConnectRdp(RdpConnectionSettings connectionSettings, CancellationToken ct)”,“Category”:null,“Status”:null} that’s the complete log, is it work ?
Check the Login to Console setting in Orchestrator and set it to Yes. This may resolve the issue if the robot is unable to establish an unattended session.
Also, ensure that the robot credentials are configured in Orchestrator if they haven’t been set up already. Without valid credentials, the robot won’t be able to perform the unattended login.
I got a last question, the older configuration it was LogIn to Console “No” and the jobs worked still yesterday in the afternoon, how could be the matter ?
This could be happen any of these Windows update, Group Policy, RDP/security policy, robot credentials, or Orchestrator configuration could have been modified.
