We have problems starting a process from orchestrator if vm instance is in log off state. It seem that the average RDP login time is over 60s which could cause this error “Executor start process failed, reason System.Runtime.InteropServices.COMException (0x80070520): A specified logon session does…

Hi, How about this. https://www.webfusion.co.uk/support/answers/Dedicated-Server/Windows/how-do-i-set-up-the-timeout-options-for-remote-desktop-connections-2078/

Link says i don’t have access to it?

So it should be possible in theory to start process even if we have logged out the robot ad vm session? In this scenario we are trying to start UIPath Studio dev robot, is there limitations with the studio robot? According to documentation only 443 is necessary to be open between orchestrator and …

Thanks! Now i can access the article. So the latest version https://www.uipath.com/release-notes/uipath-v2016.2.6442 is required to use the new parameter.

Tested with 2016.2.6442 seems to fix the issue. Didn’t receive the error after setting longer timeout in the robot vm instance.

How to increase rdp login timeout value when starting process

Help

Andrei_Pop (Andrei Pop) August 23, 2017, 7:41am 3

Please check this topic: Config RDP timeout to create user session

Let me know if it works.

Topic		Replies	Views
Orchestrator running robot on VM - RDP issues Help	8	5305	December 27, 2018
Config RDP timeout to create user session Tutorials orchestrator , robot	3	24745	February 4, 2025
Orchestrator TimeOut Issues while scheduling job from Back Office Help orchestrator	10	4764	January 4, 2019
Running Job from Orchestrator on on RDP Windows Server (Login False) does not work - Activities never time out and job never goes to fault Help orchestrator , error	10	1833	October 15, 2019
RDP Session ending after 2 hours Robot robot , question	12	1510	May 17, 2024

How to increase rdp login timeout value when starting process

Related topics