Forum Discussion

gus's avatar
gus
Contributor
9 years ago

The operation cannot be performed, because the user session is disconnected.

Hi,   I have a GUI test suite which I need to run on a remote computer according to a schedule, and I came to a problem I seem to unable to circumvent.   To put it simple, the test suite performs...
devex xtrabars
rdp
remote desktop
ribbon
tscon
  • rrivest's avatar
    rrivest
    9 years ago

    Honestly, I don't think you need a VBScript at all... Just have that generic user created with sufficient privileges on the machine, mostly with No-Screen-Saver, and connect to the machine using that account... Configure your taskschedular to run TestComplete with cmdline parameters properly, you can even launch the task manually to check it, then simply exit using the cmd I suggested... Your test will run without you being connected... you can reconnect to it and watch it without even disrupting it...  just make sure you exit properly... by redirecting the session to the console...

     

    Session id of your user is accessible through the task manager, User tab...

     

    gus wrote:

    Hi, I'm sure it helps, however I need to ask for the details. Where and how should I exit from the script with redirection? Do you mean I should replace my call to tscon with the one provided? And how can I make sure that generic user (which is our goal to implement) always runs in session 2?

     Session on which it will run depends on which you have logged in as that user...  that often depends on the amount of users accessing that PC concurrently...

     

     

rrivest's avatar
rrivest
Contributor
9 years ago

Your issue seems to relate to the ScreenSaver and  GroupPolicies.

TaskScheduler isn't a standard user, rather a system process, hence not using a "session console"

 

Your remote session works because you have an "active" console...

In order to have TaskScheduler run your test, you need to leave your session open so it is used by the task.

 

So instead of disconnecting the RDP session by script, simply exit it with a redirection so it is left open for the taskScheduler.

 

I have a generic user that has a No-Screen-Saver policy on each of my virtual machines....  it runs source code updates every night before launching nightly tests... When I set up, I connect using that account to the remote machine and exit using a cmd line : tscon 2 /Dest:Console, so the session stays open for the taskscheduler..

 

Hope this helps...

  • gus's avatar
    gus
    Contributor
    9 years ago

    Hi, I'm sure it helps, however I need to ask for the details. Where and how should I exit from the script with redirection? Do you mean I should replace my call to tscon with the one provided? And how can I make sure that generic user (which is our goal to implement) always runs in session 2?

    • rrivest's avatar
      rrivest
      Contributor
      9 years ago

      Honestly, I don't think you need a VBScript at all... Just have that generic user created with sufficient privileges on the machine, mostly with No-Screen-Saver, and connect to the machine using that account... Configure your taskschedular to run TestComplete with cmdline parameters properly, you can even launch the task manually to check it, then simply exit using the cmd I suggested... Your test will run without you being connected... you can reconnect to it and watch it without even disrupting it...  just make sure you exit properly... by redirecting the session to the console...

       

      Session id of your user is accessible through the task manager, User tab...

       

      gus wrote:

      Hi, I'm sure it helps, however I need to ask for the details. Where and how should I exit from the script with redirection? Do you mean I should replace my call to tscon with the one provided? And how can I make sure that generic user (which is our goal to implement) always runs in session 2?

       Session on which it will run depends on which you have logged in as that user...  that often depends on the amount of users accessing that PC concurrently...

       

       

      • gus's avatar
        gus
        Contributor
        9 years ago

        Oh I see, you mean to issue the tscon redirection once scheduling the task.

         

        Actually why I created two version of the tscon command is that it turned out that session id/name could not be obtained from the shell when Task Scheduler triggered the test run, even if I kept the remote desktop window open.

         

        Can you confirm the solution worked for you when you scheduled the task, instead of manually starting?