Forum Discussion

sriguda's avatar
sriguda
Frequent Contributor
8 years ago

Windows schedular fails launching Test Execute

Hi, I have installed Test Execute 12.10.... on Windows 10 machine. I am able to access scripts on this machine saved on Network drive. I am able to trigger Test Execute and run the scripts manuall...
  • tristaanogre's avatar
    tristaanogre
    8 years ago

    Again, probably has EVERYTHING to do with user privilege.  However, in Windows Server 2012 R2 (I have an instance up in front of me right now), there's not exactly a "Store" feature. So, that particular option probably doesn't really impact a Windows Server 2012 machine.

     

    Just as a note for everyone watching this thread, this is documented in the TestExecute help:

    General Options Dialog

    • With the Windows Store applications support enabled, TestExecute stops supporting several test features you may want to use:

      • Automating TestExecute via COM (to do this, you need to configure your application in a certain manner).

      • Running tests in Connected and Self-Testing Applications (the applications will not be able to connect to TestExecute).

      • You may also experience problems with various tools that launch TestExecute via COM or command line.
sriguda's avatar
sriguda
Frequent Contributor

In the support Issue submitted, suggested to disable the option, "Enable support for testing Windows Store applications (requires restart)" on TE options. I did so and it works now. Triggers schedular and runs the scripts .

 

But my question is I was running these scripts on Windows Server 2012 machine and this option was not disabled but it launced and ran the scrits fine.

 

I don't understand the difference.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
8 years ago

Again, probably has EVERYTHING to do with user privilege.  However, in Windows Server 2012 R2 (I have an instance up in front of me right now), there's not exactly a "Store" feature. So, that particular option probably doesn't really impact a Windows Server 2012 machine.

 

Just as a note for everyone watching this thread, this is documented in the TestExecute help:

General Options Dialog

  • With the Windows Store applications support enabled, TestExecute stops supporting several test features you may want to use:

    • Automating TestExecute via COM (to do this, you need to configure your application in a certain manner).

    • Running tests in Connected and Self-Testing Applications (the applications will not be able to connect to TestExecute).

    • You may also experience problems with various tools that launch TestExecute via COM or command line.
  • sriguda's avatar
    sriguda
    Frequent Contributor
    8 years ago

    Thank you so much for clarifying.