Hello CurtisDo,
Thank-you for your question.
Basically it is highly recommended to get the latest ZPX (Short for Zap-fix) version, there are a lot of new features, bug fixes, etc:
For example, the current ZPX latest version does not require to use the "zapFIXinitialize" method in the beginning of a ZPX based script.
Regarding your issue, please do the following:
1. First a checklist to handle a well encountered issue where scripts are stuck on "zapFIXinitialize":
1.1 Check Results Viewer.
1.1.2 Stop the test execution.
1.1.3 Click the Results button to open the execution results
Examine the results.
1.2 Find object errors and write them down:
1.2.1 Find General Errors and write them down.
1.3 Check if the main window gets recognized by QTP:
1.3.1 Open the Object Repository of the script and select the main parent object (the application object. Should be a “Window” class).
1.3.2 Click “Highlight in application” button.
1.3.3 If the window does not get highlighted, QTP cannot recognize the parent window.
2. Try the following solutions:
2.1.1 Restart QTP and choose to load only ZAP-fiX add-in. Disable all other add-ins.
2.1.2 Launch QTP, ZPX and ZPX Viewer as administrator (right click -> run as administrator).
2.1.3 Check if all the running applications (QTP, ZAP-fiX, ZAP-fiX Viewer) are running under the same username.
2.1.4 Close QTP, ZAP-fiX and ZAP-fiX Viewer.
2.2.1 Open QTP first as administrator (right click on the shortcut -> run as admin.).
2.2.2 Open ZAP-fiX and ZAP-fiX viewer as administrator.
3 Submit support ticket:
3.1 If none of the above helped solve the case, submit a support ticket with the captured errors from step 1 with screenshots.
Thanks,
Sasha