Forum Discussion

DiSch's avatar
DiSch
Occasional Contributor
15 years ago

TestExecute 7.52: Error at closing TestExecute after test run

Hello,



we have often following error in the Windows Eventlog at closing TestExecute after a test run:



------------------------------------------------------------------------------------------------------------------

Anwendung ("C:\Program Files\Automated QA\TestExecute 7\\bin\TestExecute.exe" /Run /Exit /ns /SilentMode

"c:\program files\prisma\testcomplete-projects\PrismaTests\PrismaTests.pjs" /project:ConsoleTest /exit

/SilentMode /el:"C:\Windows\TEMP\PrismaTestCompleteTests.mht") (PID: 1340)

verwendet Windows-Funktionalität, die in dieser Version von Windows nicht vorhanden ist.

Wenden Sie sich an den Hersteller der Anwendung, um eine aktualisierte Version der Anwendung zu erhalten.

Dies sind die technischen Informationen, die dem Hersteller der Anwendung übermittelt werden müssen:

"Eine RPC-Methode wurde für eine verbindungslose Protokollsequenz ncadg_ip_udp aufgerufen.

 Syntax und Unterstützung dieser Protokollsequenz sind in dieser Version von Windows veraltet.

Informationen zum Veralten finden Sie unter http://go.microsoft.com/fwlink/?LinkId=36415."

Benutzeraktion: Wenden Sie sich wegen einer aktualisierten Version der Anwendung an den Hersteller.

------------------------------------------------------------------------------------------------------------------

and additional this:

------------------------------------------------------------------------------------------------------------------

Fehlerhafte Anwendung TestExecute.exe, Version 7.52.678.11, Zeitstempel 0x2a425e19, fehlerhaftes Modul aqJScriptParser.dll,

Version 7.52.678.11, Zeitstempel 0x4b5d9580, Ausnahmecode 0xc0000005, Fehleroffset 0x00004f22, Prozess-ID 0x53c,

Anwendungsstartzeit 01cab379135853c7.

------------------------------------------------------------------------------------------------------------------



The test will be startet from a MSBuild script and lasts about one hour.

I hope you can help us.



I made a dump file but 199 MByte could not be added to this forum.





Thank you,



Dirk Schaumann

8 Replies

Sort By
  • DiSch's avatar
    DiSch
    Occasional Contributor
    15 years ago
    Remark:



    The used OS was Windows Vista SP2.
  • YMinaev's avatar
    YMinaev
    Staff
    15 years ago
    Hi,



    This problem is known, and it shouldn't affect the TE functionality or tests. Do you observe any issues with TE or do you just get this error?

  • DiSch's avatar
    DiSch
    Occasional Contributor
    15 years ago
    The error does not affect the test but at closing TestExecute an error dialog from Windows occurs and the process is running until the button on this dialog will be clicked.



    We want to run our TestExecute tests in silent mode therefore we need a closing procedure without an error dialog.



    Do you have a solution for our issue ?
  • YMinaev's avatar
    YMinaev
    Staff
    15 years ago
    Hi,



    What exact error dialog do you get? Can you post here an image demonstrating it?

  • DiSch's avatar
    DiSch
    Occasional Contributor
    15 years ago
    Here is the screenshot of the Windows error dialog.

    The Windows Eventlog has got the same error entries like at my first post.



  • YMinaev's avatar
    YMinaev
    Staff
    15 years ago
    Hi Dirk,



    Is UAC enabled on the problematic machine? If it is, does it help if you disable it?

  • DiSch's avatar
    DiSch
    Occasional Contributor
    15 years ago
    Hi Jared,



    UAC is enabled on the machines where the problem occurs but our tests have to run with UAC.


    As the problem does not occur frequently, UAC probably is not the cause
    of the problem.


    The Windows Vista machine was a virtual machine on a Xen Server. Since the vm with TestExecute run alone on the Xen Server no error occurs. I think it is a timing an writing problem.



    Thanks
  • YMinaev's avatar
    YMinaev
    Staff
    15 years ago
    Hi Dirk,



    Yes, timing may be the problem, however, we need to investigate it more deeply to find the exact cause. If possible, please follow the steps below to provide us with more information:



    1. Download AQtime.



    2. Install and start it.



    3. Select the File | New Project From Module... main menu item.



    4. In the Open File dialog, select the '<TestExecute>\bin\TestExecute.exe' file and click Open.



    5. If needed, specify command-line parameters for it (Run | Parameters...).



    6. Take a look at the AQtime toolbar - there is a combo box. Open it and select the Tracing | Exception Trace Profiler item.



    7. Right-click somewhere inside the Event View panel (it is opened by default at the bottom of AQtime's window) and select the Options... item.



    8. In the Options dialog that appears, set the value of the Profiling Time | Event View | General | Exceptions | Depth Shown option to 100.



    9. Click the Run toolbar button (the green arrow) or press F5 to start the profiling.



    10. AQtime will start TE and trace all exceptions that will occur in it until it is closed.



    11. Reproduce the problem and terminate TE when it occurs.



    12. Right-click inside AQtime's Event View panel and select the Save All... item.



    13. Save the contents of the panel to an HTML file and send it to us.