Hi all,

We are migrating our whole automated testing infrastructure from HP UFT11.53+ALM11.00 to HP UFT12.02& ALM12.20.
We have a Win7 64-bit VM with UFT12.02, on which Jenkins v1.624 is installed with the latest version of the HP ALM plug-in.
And we have a Win2008 64-bit VM used for ALM12.20 Patch level 1 (it's configured to use port 80, and NOT the default port 8080).
We used to have the equivalent for the v11 infra.

We've been running tests using Jenkins onto the same VM on the v11 infra, and it worked well. Now, on the v12 infra, we're getting the infamous error:

Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://ALM_SERVER/qcbin/TDConnectivity_index.html
Build step 'Execute HP functional tests from HP ALM' changed build result to FAILURE

We have been digging deep into the matter:

• We've followed the instruction given by the error message above, by installing the TDConnect with Admin rights.
• We've found the ticket JENKINS-16464, which suggested to use http://almserver:8080/qcbin/start_a.jsp?common=true (we replaced 8080 by 80, as mentionned above).
• We've opened ALL the TCP and UDP ports between the UFT and the ALM VMs.
• We used the Run Local option.

None of the above work...

What's more, we have rolled back the infra, and configured our UFT12.02 VM to connect to the old ALM11 server (with all the components installed and registered with admin rights, reboot the VM...). Jenkins is then able to run a test set.
We repeat the exact same configuration steps for the ALM12.20 server (with admin rights and all), no dice... we still get the "Could not create scheduler" message.

Any help is appreciated!
Thanks in advance.