Unable to add a Host in Performance Center

When adding a host on PC 9.x it shows the credentials popup, the event viewer shows the below error

Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10016

Date: 8/29/2011

Time: 1:26:03 PM


Computer: KCH1D068


The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18). This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This is because the DCOM server has no permissions to start

To fix this issue modify the DCOM permissions:

Start -> Run -> dcomcnfg

Expand Component Services, expand Computers , expand My Computer , expand DCOM Config

Right click on SMS Agent Host , click Properties

Select the Security tab, click Edit in the Launch and Activation Permissions section

Select System , ensure Local Launch is Allowed

Click OK, Click OK

additional details here


Right click in the ALM GUI not working

Right clicking anywhere in the ALM GUI, any module, does not function in a specific project

1) Logon to a project where right click in the GUI functions properly
2) Go to Tools>Customize>Project Report Templates>Document Templates>Document Template
3) Download the template and save to a location on the client machine
4) Log out of the project
5) Log into the project where right click in the GUI does not function
6) Go to Tools>Customize>Project Report Templates>Document Templates>Document Template
7) Upload the “Document Template” from Step 3

Right click should now be functional

Quality Center Server logs are not created anymore

Quality Center (QC) or Application Lifecycle Management (ALM) server stops writing server logs.

When the QC \ ALM server is installed on a Linux\Solaris operating system and the log files that are currently used by QC \ ALM process for writing are deleted, QC \ ALM server will stop writing new logs until it is restarted.

Restart of the QC / ALM process resolves the situation

Create ALM encrypted password for the dbid.xml file

1. Locate dbid.xml file
For example). C:\ProgramData\HP\ALM\repository\qc\Default\demo\dib.xml
It is need dbid.xml file backup

2 . In Site admin->Site projects tab->domain_name->project_name select “DB user Password” link under Project details tab.
Project is deactivated and you can type the new password
3. Remove the project
4. In Oracle Enterprise Manager edit project_db (project_name) user and type the new password (same as from step 1)
5. Restore and activate the project
The password for qcsiteadmin schema may need to be changed with a new one when using Oracle as a database in Application Lifecycle Management (ALM) 11. This can be achieved by following the next steps.
Note that the new password will be only applied to ALM user password for qcsiteadmin schema (different from project schema) and the projects password will not be affected.


Before proceeding with the following steps and making any changes in site administration, the best would be backing up the DB_USER_PASS value that is located in the qcsiteadmin database/schema DBSERVERS table, or ideally backup the whole siteadmin database(qcsiteadmin_db).

Steps to change the default ALM user password for ALM qcsiteadmin_db:

1. First the “Application Lifecycle Management User password” from Site Administration -> DB Servers Tab should be changed with the new one.
This operation updates the DB_USER_PASS column (new password encryption) in the DBSERVERS table in qcsiteadmin_db (Site Administration database/schema)
2. In Oracle Enterprise Manager edit qcsiteadmin_db user and type the new password (same as one)
3. Go and display the contents of DB_USER_PASS column (new password encryption) in the DBSERVERS table in qcsiteadmin_db (Site Administration database/schema) and copy the encrypted value.
Save it somewhere.
4. On the application Server go to the ALM deployment location. For example it would be:


There you will find the siteadmin.xml file preserving information for the created siteadmin schema.
Backup this file just in case.

with the new (updated) DB_USER_PASS value from the DBSERVERS table

5. Save the changes in the siteadmin.xml file.
6. Go to the following location on your Server:
C:\ProgramData\HP\ALM\conf and edit the “qcConfigFile.properties”

Find the places where the old Encryption of the password is written and change it with the new one. You need to focus over:

7. Restart the HP ALM Service from Services.
8. Try logging to ALM Site Admin page and to any ALM project.
Note that this change does not affect projects’ user password and they will keep the old ones.

Verify if SAP Solution Manager is configured to integrate with HP ALM

If there are indications showing that SAP Solution Manager server is not configured correctly:

-The “Connect to HP QC project” option is missing in the menu of the Project Administration section of SAP Solution manager (SOLAR_PROJECT_ADMIN transaction).


-There is no calculated URL address for BPCA_WS_API (related to BPCA integration).


The reason is that the SAP Solution Manager server was probably not correctly configured.

To fix this issue, the HP QC Add-on should be installed on the SAP Solution Manager system. This add-on is part of the HP QC Adapter license (in the past this was installed on the GTE server).
The documentation for the HP QC adapter configuration is available in the following SAP guide: https://service.sap.com/~sapidb/011000358700000210952014E.PDF (SAP Solution Manager Adapter for SAP Quality Center by HP.pdf).
The document for the “BPCA integration” (complement to the above configuration to additionally allow BPCA integration) is available in the SAP guide: https://service.sap.com/~sapidb/011000358700000043712014E.PDF (Business Process Change Analyzer How-to Guide.pdf).

Access to the SAP documentation from SAP domain requires an SAP account and it is recommended to consult SAP support for further help with SAP Solution Manager configuration.

Creation of logical ports in SOAMANAGER failed accessing the URL of EI webservices of HP ALM

During the creation of logical ports in SOAMANAGER of SAP Solution Manager, errors can be seen:

– Logical port creation error: “Error in HTTP Framework 404 Connection”


– Proxy error after setting proxy settings during creation of logical port: “Error in HTTP Framework 500 Internal Server Error”.



SAP server (and proxy server) are not able to access the URL of HP Application LifeCycle Management server.

ABAP program – RSHTML01 (run via SE38 transaction in SAP Solution Manager) can be used to check if the URL of HP Application LifeCycle Management server is accessible from the server side of SAP Solution Manager system.


Error Message: “Unspecified Error” appears in the automatic runner

When you attempt to launch a UFT test from ALM 11 the error “Unspecified Error” appears in the automatic runner. This happens when UFT is open on the target machine and does not matter if it has a test loaded or not, and a limb attempts to start the test remotely. Happens only for remote execution

The reason is because the DCOM user does not have enough permissions

To resolve this issue, Switch the user to “launching user”

In order to change it, please follow these steps:

Go to Start -> Run

Type: dcomcnfg

Navigate through the following path:

Component Services -> MyComputer -> DCOM -> right click HP UFT -> properties -> identity tab

Select the “launching user” option.