A specified logon session does not exist

jobs
p_qa
faulted

#1

I have a VM with Windows server 2016, I provisioned a robot in the demo environment of UIpath.
This was working fine, but each time I ran the process my RDP session ended.

Because I want to see (for testing reasons) what the process is doing I allowed the number of RDP sessions on the server to more than one. I also changed the “LoginToConsole” setting to false in “UiPath.settings”. I also configured the RDP session timout to 120sec.

I still get the following error in Orchestrator. The local robot logs shows nothing, so the process is not started at all. What is going wrong?

Executor start process failed, reason System.Runtime.InteropServices.COMException (0x80070520): A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)\r\n at UiPath.UiSystemClass.OpenInteractiveWindowsSession(String bstrUser, String bstrPassword, UiOpenSessionFlags nFlags, String bstrApplication, String bstrAppArguments, Int32 nDelayMs, Int32 userToken, UiGenericOptions options)\r\n at UiPath.Core.Setup.OpenInteractiveWindowsSession(String username, String password, OpenSessionFlags flags, String application, String arguments, Int32 userToken, Int32 preferredWidth, Int32 preferredHeight, Int32 preferredDepth)\r\n at UiPath.Service.Impl.Executor.StartProcessInSession(Guid executorInstanceId, String username, String password, OpenSessionInfo sessionInfo, IntPtr userToken)\r\n at UiPath.Service.Impl.Executor.<>c__DisplayClass13_0.<<Start>b__0>d.MoveNext()"


#2

Hi,
In case you didn’t come across this post.
Still same issue let @Andrei_Pop know.


#3

Hi, thank you.
Yes, I already changed that to 120seconds… I still got the same error.
Do you know a solution, @Andrei_Pop?


#4
  • check if there are any logged sessions on the robot machine (log off all of them and retry)

  • change in settings LoginToConsole from true to false and let me know if you still encounter the problem


#5

Via Task manager I logged of every user (except the user I was working with). The LoginToConsole was already put to false.
When I try to run the process (just showing a simple MessageBox), I can see a user being created on the server, but the process is still giving me the same error, and the process is not run.


#6

Got the same problem. Machine With win10 Ent. Logged out all users and closed RDP session receiving this: Executor start process failed, reason System.Runtime.InteropServices.COMException (0x80070520): A specified logon session does not exist… error. But when have opened RDP to this PC all Jobs works perfectly. (UIPATH_SESSION_TIMEOUT=120 seconds and LoginToConsole=“False”)


#7

We also are facing issue with the robots where the robots stopped suddenly on one fine day. The error message thrown read:
Robot : VM 2 Robot 5
Info : “Executor start process failed, reason System.Runtime.InteropServices.COMException (0x800700AA): The requested resource is in use. (Exception from HRESULT: 0x800700AA)\r\n at UiPath.UiSystemClass.OpenInteractiveWindowsSession(String bstrUser, String bstrPassword, UiOpenSessionFlags nFlags, String bstrApplication, String bstrAppArguments, Int32 nDelayMs, Int32 userToken, UiGenericOptions options)\r\n at UiPath.Core.Setup.OpenInteractiveWindowsSession(String username, String password, OpenSessionFlags flags, String application, String arguments, Int32 userToken, Int32 preferredWidth, Int32 preferredHeight, Int32 preferredDepth)\r\n at UiPath.Service.Impl.Executor.StartProcessInSession(Guid executorInstanceId, String username, String password, OpenSessionInfo sessionInfo, IntPtr userToken)\r\n at UiPath.Service.Impl.Executor.<>c__DisplayClass13_0.<b__0>d.MoveNext()”


#8

+1 - again :frowning:
was more stable since a software upgrade - not anymore, unfortunately.


#9

+1 (@ArneDeProft)

Windows 2012R2, UiPath Robot 2016.2.6379.27659.

  • Running processes from Orchestrator works in an active RDP session (one I’m actually logged in to at the time).
  • When disconnecting the session (leaving only the robots user logged on, but disconnected the RDP session) I get the error above.
  • When there’s no RDP session to begin with (0 users logged on), I get the exact same error.

Did anyone find a resolution for this?


#10

I am encountering this issue, and have tried all suggested methods given in this forum and windows forums, but to no avail. do you have any suggestions?


#11

I am encountering this issue, and have tried all suggested methods given in this forum and windows forums, but to no avail. do you have any suggestions?


#12

Hello,
Since last windows update I got this message too from all environment… When uninstall last security update, Orchestrator resume correctly, but I am forced by firm to pass security update, someone find a reason and a solution about this?


#13

Same here - we started to receive this error after the latest patches installed yesterday on a VM with Win2012R2


#14

Hello,

Same issue for us. After the latest Windows security update installed yesterday (KB4088787), the robots cannot login to the server anymore. Nothing else has chagned. The error is the same as OP had, that the logon session does not exist.

We are currently in the process of uninstalling the update, as our colleagues from another country confirmed that had solved the issue for them.

Would love to know if there is a solution to fix this, other than freezing Windows updates.


#15

Hi @tuokyh,

We are aware that the latest Windows update did some changes in the library for RDP and we are working on a fix that will be released as soon as possible. For now the workaround is to uninstall the update, but this won’t be necessarily once the fix would be released.

I’ll keep you updated.

Thanks,
Viorela


#17

Uninstalling the update KB4088787 mentioned by @tuokyh doesn’t work for us, we get the same error. Are there any other updates that need to be uninstalled (until the fix is released)? Thanks!


#18

@florin.stan
Uninstall kb4088876.


#19

Anyone using Windows 7? What update that caused this? fyi, i dont have KB4088787 and KB4088787 installed


#20

I also have this problem! After I uninstalled KB4088876, the problem unfortunately persists. I do not have KB4088787. As others have asked I wonder if there are any other updates too that could be causing this?

Any of the following maybe?

KB4074594
KB4089187
KB4088879
KB4074837
KB4073700
KB4074736
KB4074597

At least these are the ones I see from the last update, which is when things started to go downhill…


#21

Hi @ovi , when can we expect a patch? Any news?