Running job issue "A specified logon session does not exist. It may already have been terminated" -

Help Orchestrator
1

Hi,

Orchestrator 2018.3 (actually upgrading to 2019.10).
Sometimes, when a job run immediatly after another one finishes, we got the Error “Executor start process failed, A specified logon session does not exist. It may already have been terminated”. Looks like the first RDP session did not manage to logoff correctly before the second job start.

We would try the UIPATH_SESSION_TIMEOUT increase fix but we can’t find on which machine to put this : Orchestrator server or UIRobot machine ?

Regards,
Cedric.

2

@cpage - recently any VM robot user password got changed/updated? if yes - pls update the robot password with latest password.

3

Hi @GBK,

not a password issue. Error is very random.

4

@cpage - please login into the VM and check the logon/logoff activities in event viewer. it might help you!

5

Thx. But i just want to test the UIPATH_SESSION_TIMEOUT variable. Should it be set on Robot Machine or on ORCH server ?