Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    9
  • Views views
    101
  • Users 0 members are here
Related
Options

ALM QC 24.1 can not execute automated UFT Testcase remotely

Toni Goriwoda

Hi,

we have installed Labservice 18 on our Testclient. DCOM Permission and createGlobalObjects is set and UAC is deactivated.

In UFT is "allow other products.." set.

The Client is registered is QTP Client in Labmanagement. 

We start the remote execution and got this error:

An error occurred while executing a test Exception Unable to connect the testing tool to the requested ALM/QC server. Error from UFT One: Die COM-Klassenfactory für die Komponente mit CLSID {C5CBD7B2-490C-45F5-8C40-B8C3D108E6D7} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80040154 Klasse nicht registriert (Ausnahme von HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))..

Has anyone an idea?

Tags:

  • Suggested Answer

    0  

    On the Labservice / UFT host machine, try UFT UI , see if it can connect to the ALM server,

    if not, then register  ALM Client components on the Labservice host machine, either by ALM Client launcher with parameter ?common=true or by the link in the <alm server url>/qcbin/CommonMode_index.html  ( ALM server home page , the <url>/qcbin/   -> Tools -> "ALM Client Registration" -> "Register ALM (32-bit)" ) in a browser as below screenshot shows.

    if the issue still persists, open a ticket to UFT support.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.