Category Archives: Quality Center

HP Quality Center troubleshooting tips and tricks

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

Advertisements

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)
    • INTERACTIVE
    • 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”).

Download run results files from ALM using OTA

This can be done using the ExtendedStorage property of the Run object.

Note: it works for both normal tests and BPT tests

RunID = 433
downloadPath = “C:\Temp”
qcurl = “http://10.10.14.15/qcbin
qcdomain = “DEFAULT”
qcproject = “DemoProject”
qcuser = “admin”
qcpass = “”

if IsOTAInstalled() then
set QCConnection = CreateObject(“TDApiOle80.TDConnection”)
QCConnection.InitConnectionEx qcurl
QCConnection.ConnectProjectEx qcdomain, qcproject, qcuser, qcpass
If not QCConnection.Connected then
Msgbox “Not connected. Exiting…”
Wscript.Quit
else
Set auxFilter = tdc.RunFactory.Filter
auxFilter.Filter(“RN_RUN_ID”) = RunID
For Each auxRun In auxFilter.newlist
Set extStorage = auxRun.ExtendedStorage
extStorage.ClientPath = downloadPath & “\” & RunID
extStorage.Load “”, true
Next
QCConnection.Disconnect
QCConnection.Logout
QCConnection.ReleaseConnection
End if
else
Msgbox “OTAClient.dll not registered. Exiting…”
End if
Function IsOTAInstalled()
IsOTAInstalled = true
On Error Resume Next
set QCConnection = CreateObject(“TDApiOle80.TDConnection”)
if err.number <> 0 then IsOTAInstalled = false
On error goto 0
End Function

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:

update LAB_MAINTENANCE_TASKS set LTASK_STATUS=’N’ where LTASK_NAME like ‘%PAL%’

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