Forum Discussion

jimpson's avatar
jimpson
Contributor
10 years ago

Why could TestComplete/TestExecute fail to work with IE 11 in a Windows Server 2012 R2 environment

I have an environment full of Server 2012 R2 Machines.  If I force the GPOs down on them and restart them, TC/TE will work.  If I neglect to force the GPO down (which shouldn't make a difference), TC...
jimpson's avatar
jimpson
Contributor

I've managed to narrow this problem down a little further...  So here goes.

 

I previously had a GPO in place to launch our tested application and TestExecute when the machines were started.  If I disable this GPO, I have to manually start both the tested application and TestExecute.  When the TE application is started manually, the applicaiton will run the scripts without failure.  If I allow the GPO to start the tested application and TE, then the test will launch Internet Explorer ( a step required to generate data for the tested applicaiton) and then it appears to lose scope of the the IE browser.

 

When TE and the tested app are launched via GPO, and the test fails, I can then cause a crash with the TE applicaiton by simply right clicking the TE system tray icon and using the applicaiton's built in exit command.  Exiting the application in this manner (the intended manner), causes the crash, which reports a problem with asComm in TestExecute. 

jimpson's avatar
jimpson
Contributor
10 years ago

Here is the error I get when I shutdown TE after a system restart:

 

aqCommError.PNG

 

Once I restart the TE client when this error occurs, I can continue as I would have been able to normally.

  • jimpson's avatar
    jimpson
    Contributor
    10 years ago

    Here is a list of the things I have tried to remedy this situation:

     

    -Uninstall / Re-install TE with admin privileges

    -Manually start TE (This works)

    -GPO start TE from the executeable path (doesn't work)

    -GPO start TE from a custom link path that permits admin level privileges (doesn't work)

    -Scheduled Task start TE (doesn't work even when launched with highest privileges

    -Batch file start TE (doesn't work)

    -Delayed Scheduled Task start TE (doesn't work)

     

    Is there a debug mode for TE that would allow me to see why this aqComm.dll is failing?  If I could see that, I could possibly fix any potential permisssions issues with the app, or provide more information about what might be causing the issue...

    • TanyaYatskovska's avatar
      TanyaYatskovska
      SmartBear Alumni (Retired)
      10 years ago

      Hi,

      You can try using the ReportGenerator tool shipped along with TestComplete and TestExecute. Here are the steps to get the crash report:

      1. Run the Report Generator tool located in <TestExecute>\Bin\ReportGenerator.exe.
      2. Select the "Launch/attach to TestExecute" option.
      3. Reproduce the problem.
      4. Click the "Generate..." button in the Report Generator tool and save the report to a local folder.

      To help you resolve the issue, I would recommend that you contact our Customer Care team and send them the report, as well as the description of the issue: http://support.smartbear.com/product-list/

  • joseph_michaud's avatar
    joseph_michaud
    Moderator
    10 years ago
    This may be a silly question but... in the image showing the aqComm.dll error, did you blank out part of the destination path? Or does the path really start with 

    C:\Users\Auto                \...
    • jimpson's avatar
      jimpson
      Contributor
      9 years ago

      I blanked out the path.