Tag Archives: Quality Center

Initialization of the ALM Octane Server

If you are not getting past the initialization of the ALM Octane Server and getting database connection issues like

error: url=’jdbc:mercury:sqlserver://′, dbType=MSSQL, userName=’sa’]. Error: Connections could not be acquired from the underlying database!

The root cause for this is the SQL services.The SQL Agent and Browser are not running, causing the connection issue between the DB and the Octane server.


Copy test with requirement coverage

User wants to have all the test cases with the linked requirement from 3 different projects to one new project.

• Go to Management module (old projects)
• Go Libraries
• Create a new Library
o Select all the requirements
o Select ‘Test covering selected requirements’
• Create a baseline
o Check the logs

• Import a library
• Check the logs
This copies the test and its requirement coverage as your user has requested.


The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index

Migrated our HP ALM to new windows server and sql server. Was able to migrate HP ALM to version 12.55 however projects fail to upgrade.

Getting the below error message after upgrading a project,

Exception occurred. Message: [Mercury][SQLServer JDBC Driver][SQLServer]The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name ‘dbo.LISTS’ and the index name ‘LS_LOGICAL_NAME_IDX’. The duplicate key value is (hp.qc.plan-status.imported).

In this case the issue is because there is a duplicate key in [dbo].[LISTS] table.

You may need to run the following query in order to identify which is the duplicated one : select * from [dbo].[LISTS] where ls_logical_name=’hp.qc.plan-status.imported’

In this case it seems that the value for the LS_NAME had been modified, the default value is "Imported" and in your case is "Feedback Provided".

So the application notices the original value does not exist so it insets it (as seen in the last upgrade attempt, after running it another one was created) and consequently this causes the index duplicate error.

For fixing this issue it is necessary to update the LS_NAME to the original value, then run the upgrade process and later you can update the records again and have the customized as desired. This will not affect the data that is already in the entities .

After that you may need to follow the next steps in order to resolve the issue:

To update the records a simple query like this can be used:
Update [td].[LISTS] set LS_NAME ‘Imported’ WHERE LS_ID = ‘355’


HPE Diagnostics User Interface freezes or hangs

Having launched the HPE Diagnostics User Interface (UI) by clicking on “Open Diagnostics” (or “Open in This Window”) and entering a user name and password, performing an action such as viewing the data for long periods (days or weeks) for all Java Probes may result in the UI freezing and no further actions being possible. This issue may occur in a larger Diagnostics environment where there are many Mediators and numerous probes.

Once the Diagnostics UI has frozen no recovery is possible and the browser tab displaying the UI must be closed. The UI can then be opened in a separate browser tab (or new browser instance) however it is likely that the freeze behavior will re-occur.

A possible cause is that the Java applet which runs the Diagnostics UI has insufficient memory such that while the UI is performing the user action, the applet process runs out of memory and terminates. When this process terminates, the UI remains visible in the browser but is no longer functional.

To confirm that the Java applet process is terminating, open the Windows Task Manager and locate the process named “jp2launcher.exe”. This process will appear while the Diagnostics UI is being initialised (after the user name and password are validated):

image text

If the “jp2launcher.exe” is no longer visible when the Diagnostics UI freezes, then the process may have run out of memory.

A workaround for this issue is to increase the heap (memory) available to the Java applet. This can be done by modifying the Java runtime parameters as follows:

1) Open the Windows Control Panel and search using “Java” to locate the “Java (32-bit)” Control Panel entry. Click on the entry to open the Java Control Panel:

image text

Note: If there is no “Java (32-bit)” Control Panel entry this may be due to there being multiple Java versions installed on the client platform. Locate the Java 32-bit installed in a folder under “C:\Program Files (x86)” (typically “C:\Program Files (x86)\Java\jre7\bin”) and execute the file “javacpl.exe” using right-click “Run as administrator”.

2) Click on the “Java” tab and then on the “View” button to open the “Java Runtime Environment Settings” dialog.

3) The default heap size is typically 256MB however this may be system dependent. The actual process memory size can be seen in the Windows Task Manager before the process terminates. Specify a larger heap size and test to see if the UI freeze remains present – increase as needed. The following example confgure a 700MB heap however up to 1GB (“-Xmx1G”) may be used (as this is a 32-bit process memory is limited):

image text


Error: “Access is denied” when running QuickTest SAP scripts remotely

Error “Access is denied” when running QuickTest SAP scripts remotely from TestDirector on a local machine.

Other things that can occur are:

  • On the QuickTest machine:
    • QuickTest SAP UI does not open.
    • QTBP.exe process never terminates.
    • “RPC server is unavailable” error message may appear.

  • On the TestDirector executing machine:
    • “connecting..” message remains on the Test Run Scheduler indefinitely.

This may be due to not having the latest build of QuickTest/SAP or DCOM is not configured correctly.

To resolve this issue
Configuring DCOM for QuickTest SAPThe user name and password used to log onto the TestDirector machine must be identical to the one on the QuickTest machine with permissions to the common directory and QuickTest (if not you must create the identical user on the QuickTest machine).

On the QuickTest machine:

  1. Go to Start -> Run and type “dcomcnfg” (without quotes).
  2. From the list of Applications, click on Quicktest for R/3 testcase.
  3. Click <Properties>.
  4. Under the Location tab, verify the “Run application on this computer” option is selected.
  5. Under the Security tab, verify you have the Custom option checked for all three items.
  6. Under “Use custom access permissions,” click <Edit> and verify you have the following entries; if not, you can add them by clicking <Add>.

    • SYSTEM
    • Everyone
    • User logging into the machine (for example, kgurusamy (Kalidass Gurusamy), again, the user must be identical to user logged onto TestDirector machine)
    • Administrator

  7. Repeat step 6 for “Use custom launch permissions.”
  8. Under the Identity tab, verify you have the Interactive user checked (instead of “The Launching User”).

Error when resetting a valid ALM Connection URL in PC Servers module of ALM Lab Management project

In the Lab Management project (“LAB_PROJECT” project in “DEFAULT” domain available in http://<server&gt;:<port>/qcbin/start_a.jsp?projectType=LabManagement) of Application Lifecycle Management (ALM), one of the configurations required for allowing integration of Performance Center (PC) server with ALM server is in the ALM Connection button available in the Servers\PC Servers module. In ALM12.0x\PC12.0x, using this button more than once to set a valid and available URL of ALM server will cause a popup error message: “Host is unreachable. Please ensure that host’s name is correct.”

This is a defect in PC12.0x.

If there is a need to reset this ALM Connection settings after having it already changed in the same ALM session, it is recommended to logout and login back from the Lab Management project and then try to reset ALM Connection settings (it is recommended to avoid changing this setting more than once in a single ALM session).


Performance issues with large number of active projects on Oracle

The ALM environment may experience slow performance for a period of time, and new database connections may be refused.

This problem may affect large ALM environments (over 500 active projects) configured to work on an Oracle database. Both ALM-PC and pure ALM environments may be affected.
PC’s PAL orphan maintenance task connects to the schema of each active project every predefined interval (default value is 1440 minutes).
This can result in a large number of open database connections which can cause slow performance until the database connections are closed.

To fix this issue

Disable the PAL maintenance tasks.
To disable the tasks, execute the following SQL query directly on the LAB project schema: