Issue while integrating HP ALM 12.6 with Bamboo using ALM for Bamboo plugin
Issue #8
resolved
I am trying to integrate the ALM with Bamboo using HP ALM plugin. As suggested by the site : http://www.autotestingtools.com/alm-task-for-bamboo have configured the required plugin at bamboo server and installed remote agent with client registration in my local machin, where ALM is installed.
But while running the build plan in bamboo I am getting below error :
Unable to cast COM object of type 'System.__ComObject' to interface type 'TDAPIOLELib.TDConnection'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{62D83266-71EF-4F8B-8AE6-661D614D0769}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
Could someone help me to find a resolution for the same.
Thanks in advance!
Comments (5)
-
repo owner
-
reporter
Thanks a lot for the details.
I have tried all the steps mentioned above. Installed the Client components with all the required permissions and registered them via Tools option in ALM. But still getting the same error :
Unable to cast COM object of type 'System.__ComObject' to interface type 'TDAPIOLELib.TDConnection'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{62D83266-71EF-4F8B-8AE6-661D614D0769}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
-
reporter
We have a bamboo server where build plan is configured and a client server where th ALM is installed. The remote agent has been running in the client machine. We have done the below installations in client.
- Log in to HP ALM and Locate the add-ons page and find HP ALM Client Registration with the link Register HP ALM.
- HP ALM Client Registration enables you to deploy and register the following ALM components on a client machine:
- HP ALM Client components HP ALM Site Administration Client components.
Should we have to so the same at server side as well?
-
repo owner
When you get error message like "No such interface supported", usually it means your QC/ALM client doesn't register correctly. Need to do it again.
- Add in site administrator, Site configuration Tab the parameter DISABLE_COMMAND_INTERFACE and set it to "N".
"If this parameter is set to "Y" (default), only users be longing to the TDAdmin group can use the OTA Command object. If it is set to "N", any user can use it.If it is set to "ALL", no users can use it. For more information, refer to the HP Quality Center Open Test Architecture API Reference."
-
Open ALM-> Tools -> Help -> Open Add-In Page -> Install TDConnect (for connectivity) would resolve the issue. It worked for few users.
-
OTA Client Registration steps http://automationtestingutilities.blogspot.com.au/2013/12/IntegrationWithQCorALMusingALMServiceWrapperPart1.html?m=1
-
repo owner
- changed status to resolved
OTA Client registraion issue
- Log in to comment
The Bamboo remote machine where the build plan will run, must have HP Client registered. This agent is the one from which connection to the HP ALM will be made.
Log in to HP ALM and Locate the add-ons page and find HP ALM Client Registration with the link Register HP ALM.
HP ALM Client Registration enables you to deploy and register the following ALM components on a client machine:
HP ALM Client components HP ALM Site Administration Client components
For a list of the tools for which you must register ALM on a client machine, refer to the HP Application Lifecycle Management Installation Guide.
Installation Instructions:
Log on to the machine as a local user or a domain user with administrator privileges. Ensure that you have the file system and registry permissions listed below. Register and deploy components on your client machine: Click Register HP ALM below for ALM Client components. Click Register HP ALM Site Administration below for ALM Site Administration Client components. Note:
After components are registered on the client machine by a user with administrator privileges, users without administrator privileges can start ALM client components.
Required Permissions:
You must have the following file system permissions:
Full read and write permissions on the HP\ALM-Client deployment folder. This is located at: Windows 7, 2008, 2008R2: %ALLUSERSPROFILE% Windows XP: %ALLUSERSPROFILE%\Application Data Full read and write permissions to the Temp (%TEMP% or %TMP%) directory. The installer program writes installation and log files to this directory. This is generally located at: Windows 7, 2008, 2008R2: C:\Users\<username>\AppData\Local\Temp Windows XP: C:\Documents and Settings\<username>\Local Settings\Temp You must have full read and write permissions on the following registry keys:
HKEY_CLASSES_ROOT HKEY_CURRENT_USER\Software HKEY_LOCAL_MACHINE\SOFTWARE
Example: https://<almserver>/qcbin/addins.html
Thanks Vikas Borse