Forum Discussion

Jaswanth's avatar
Jaswanth
Occasional Contributor
7 years ago
Solved

Unable to launch Test Execute/Test Complete from another Java Application(Non-admin) mode in Win 10

This issue is found specific only to Test Execute and Test Complete(both version 12). I'm able to launch any other application from my Java application(Also in Non-Admin) apart from these two. The error that I get is CreateProcess error=740, The requested operation requires elevation. Are TE and TC always run in admin mode even when the Run as Admin option is turned off? Issue is specific to Win 10, works fine in Win 7.

  • tristaanogre's avatar
    tristaanogre
    7 years ago

    All that code will do that you showed me is run the application... it won't execute any tests or anything like that.  I'm assuming you're aware of that.

     

    In any case, go to Tools | Options | General... there's a flag there for "Enable support for testing Windows Store applications".  If that is checked, as per the help, you may have issues... see below.


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

    • Automating TestComplete 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 TestComplete).

    • You may also experience problems with various tools that launch TestComplete via COM or command line.

    EDIT: What cunderw mentions is relevant as well.  You need to launch the app as a cmd command line, same syntax you would use if you ran this under Windows Task Schedular.  Thanks, Carson!

  • cunderw's avatar
    cunderw
    7 years ago

    Still though, the way you're launching is it not working, most like due to something with UAC like tristaanogre mentioned. The windows store application support could be to blame here as well. 

11 Replies

Sort By
  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    No, it doesn't always require elevation... but it depends, somewhat, on what you are trying to do.  Certain tasks, functions, etc., being executed within TestComplete may require admin access to the OS.  

    • Jaswanth's avatar
      Jaswanth
      Occasional Contributor
      7 years ago

      Can you tell me how I can avoid this? 

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        7 years ago

        Short answer:  No..

         

        Why?

         

        Because I don't know what this other Java application is, what it does, what your intention with it is, what you environment configuration is, what settings you have turned on or off in TestComplete.

         

        Now... if you provide more data, perhaps we can help.  As it is, you're trying to run TestExecute and/or TestComplete through some unknown Java application.  I know it's possible to trigger TestExecute and TestComplete tests through other applications (many users use Jenkins, Team Foundation services, and other test management tools) but I do know that there are many requirments and setups to do so.  Without knowiing more about your Java application and what you're trying to do, I really don't know the best way to help you except to suggest that you elevate the permissions of your Java app so that TE/TC will also run elevated.  It's actually not unusual for users to run TC/TE as admin since many times automated testing requires access to higher-privileged areas of applications and OS environments.

  • helmer's avatar
    helmer
    Contributor
    7 years ago

    I have to same problem. My Java Application is a Jenkins slave. And I see the same error message when I execute the TestComplete plugin step.

    I also run Windows10, I elvevated the rights of Java, Jenkins and also TestComplete. I tried with TC11&12. I tried with a almost empty project suit. Nothing helped.

     

    The same Jenkins job works with Windows7 virtual machine.

     

    Also I can launch TestComplete with a Jenkins cmd line step. But I really like the TestComplete setp because it takes care of the results as well.

    • helmer's avatar
      helmer
      Contributor
      7 years ago

      I read the solution from tristaanogre again. Unchecked the Windows store option and now it works! Awesome.

      • tristaanogre's avatar
        tristaanogre
        Esteemed Contributor
        7 years ago

        Good to know that fixed it! It was an educated guess but it seemed like the likeliest solution.  Thanks for replying that it worked!