Micro Focus QTP (UFT) Forums

Full Version: identification of java window fails
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Dear all,

i have a problem with a qt-script. One of the first steps within this script is the identification of the running java application with the following command:

JavaWindow("Window Name").Exist(1)

In the test results the following is documented then: Object does not exist.

When i start the script the corresponding java aplication is already running.

Interesiting is, that the same script works on other computers.

What can be the problem here?

Best regards,

Oliver
This behaviour occurs when the AUT is opened before QTP. Please check if this is the case.
Hi, what is AUT?
AUT = Application Under Test

btw...it's always advisable not to give out your clients/customers name in public directly or indirectly... you must have signed an NDA right?

you can edit your post...
Hi, this was not the problem. I found out, that the following environment parameter was disabled:

_JAVA_OPTIONS: -Dawt.toolkit=mercury.awt.awtSW -Xrunmicsupp -Xbootclasspath/a:C:\Program Files\Common Files\Mercury Interactive\SharedFiles\JavaAddin\classes\;C:\Program Files\Common Files\Mercury Interactive\SharedFiles\JavaAddin\classes\mic.jar

the name _JAVA_OPTIONS was written like X_JAVA_OPTIONS. But when i remove the X and activate this enivironment parameter, it is no longer possible to start the AUT. It triggers the error "Could not create java virtual mashine". Could this librarys be the problem?

Best regards,

Oliver