Tag Archives: Performance Center Troubleshooting

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://192.168.10.190:1433′, 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.

Advertisements

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

TARGET PROJECT:
• 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).
Failed SQL: /* ~~QC */ CREATE UNIQUE NONCLUSTERED INDEX [LS_LOGICAL_NAME_IDX] ON [LISTS]([LS_LOGICAL_NAME])

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

Script of Siebel Open UI application is failing during replay

Script of Siebel Open UI application is failing during replay on the first or the second iteration due to not captured correlation values.

Siebel correlation library need to be used to allow successful correlation of Siebel specific dynamic values.

The issue could appear if not all needed steps are performed to enable correlation with Siebel correlation library.

For example if the library file ssdtcorr.dll is copied into the bin folder of the product installation but but Siebel correlation rules file WebSiebel77Correlation.cor is not imported in recording option’s correlation node this can lead to correlation values not being captured correctly.

Siebel has released a correlation library file as part of the Siebel Application Server version 7.7. This library is available only through Siebel. The library file, ssdtcorr.dll, is located under the siebsrvr\bin folder for Windows and under siebsrvr/lib for Linux installations.

The library file, ssdtcorr.dll, must be available to all machines where a Load Generator or Controller reside.

Please follow all of the steps listed below to enable correlation with Siebel correlation library.

1. Copy the DLL file into the bin folder of the product installation.

2. Open a multi-protocol script using the Siebel-Web Vuser type.

3. Enable UTF-8 support in the Recording Options > HTTP Properties > Advanced node.

4. Open the recording option’s Correlation node and click Import. Import the rules file,

WebSiebel77Correlation.cor, from the \dat\webrulesdefaultsetting folder. If you are

prompted with warnings, click Override.

To apply Siebel correlation library rules for existing script, the script need to be regenerated.

Not able to upload the scripts to ALM 11 UI

The Upload script functionality is throwing an error "Script upload failed. Error: Object reference not set to an instance of an object " when trying to upload the script thru ALM-PC UI.

Patch 18 was installed on top of ALM 11 and the relevant ALM client was downloaded on PC server. Upon running the System Health check, the issue was identified as OTA Client version mismatch. The PC server has OTA client related to patch 18 and the PC Host has OTA client related to patch 10.

Run the ALM Client uninstaller on PC server. The utility can be downloaded from KM1400068. Re run the System Health check after ALM client is uninstalled from PC server. This should fix the script upload issue.

Bookmarks and Breakpoints are lost after “Save As” operation in VuGen 12.01

VuGen script bookmarks and breakpoints are lost after executing a "Save As" operation in VuGen 12.01.

This issue appears on Windows Server 2012 R2 and Windows 8.1 Operating Systems.

The problem is related to McAfee antivirus running on the machine on which VuGen is installed.

Please disable McAfee antivirus to overcome this issue.