ALM Web Client: On click on the copy icon for an ALM req the browser hangs

ALM Web Client: On click on the copy icon for an ALM requirement the browser just hangs and have to be restarted
– The copy/paste issue will only occur if all of the following apply:The user has defined a view with categories and is using hierarchical mode rather than flat
– The currently selected item in the tree is a category and not a real requirement under a category.
Therefore using the copy/paste option in flat view, with no categories, or when a real requirement is selected will work without causing the UI to hang.
– Always use the copy/paste in the ‘Actions’ menu in the main toolbar which appears whenever a requirement rather than a category is selected in the tree.
– Push for use of the .NET Desktop client for copying requirements especially as from ALM 12.50 the WEB UI client will no longer be supported.

How to check if ports are opened with power shell script

There are restrictions to use the telnet protocol in company networks, it is disable due to security policies. When working with ALM installation and integration with other tools,  Network connectivity is critical to establish the communication between different hosts,  which is made trough different network ports. 

In windows environments you can use power shell to run scripts for verifying if the port of a host is opened,  this will work for databases servers , Application servers.

The port number from this list: ALM Port list

Important: If the port is not in the above list, the software was customized to not use the default port, please check the server/software admin.

To use power shell please try the following:

1. Download the Power shell script attached to this article, copy it into a notepad and save it as Checkport.ps1
2. Make sure the Script execution is not disabled, if it is disabled please execute the following command in power shell:

set-executionpolicy unrestricted

3. Run the script through the power shell command line:

<Script path>\CheckPort.ps1 -ip IpAddressOftheHost -port PortNumber

How to handle Version Control issues in ALM

Version Control entities cannot be checked out, can’t be checked in, or an undo check-out cannot be performed. Other issues may be GUI errors when doing any VC related activity.
In some cases the user who checked out an entity may not be available. Because all entities must be “checked-in” before project upgrade this utility will check those items in.
The ALM VC (Version Control) Alignment utility aligns VC data. This pertains to the check-out user, status, VC history, and their related tables.
The utility can sweep all VC entity types regardless of their VC status, only effect checked-out entities, or effect a single entity
Before using the ALM VC Alignment utiliity read the documentation: ALM VC Alignment Utility.pdf
Obtain the ALM VC Alignment utility from here:

How to generate a Heap and Thread dump in ALM

The heap dump are useful to find cache, and memory issues in ALM , by generating the heap dumps and thread dumps, support can review what is on the ALM process memory and move forward with the investigation of the memory leaks.

How to Take Heap Dump of QC Service

  1. Download PsExec (Google search for it if it is not found in the following URL
  2. Put PsExec.exe in C:\Program Files\HP\ALM\java
  3. Run CMD.
  4. Issue the 4 following commands. Change your drive letter in case is not C:\, and look for the install directory of ALM that contains java folders:
    1. C:
    2. cd C:\Program Files\HP\ALM\java
    3. set JAVA_HOME=C:\Program Files\HP\ALM\java
    4. psexec -s “%JAVA_HOME%\bin\jmap.exe” -dump:format=b,file=heap.bin 12868
    5. replace 12868 with the PID (Use Task Manager)

image text
Select View> select Columns

image text

Then locate the ALM.exe PID column and replace it in the above command

File heap.bin will be dumped in C:\windows\system32

How to Take Thread Dump of QC Service

  1. Download PsExec (Google search for it if it is not found in the following URL Put PsExec.exe in C:\Program Files\HP\ALM\java
  2. Run CMD.
  3. Issue the 4 following commands. Change your drive letter in case is not C:\, and look for the install directory of ALM that contains java folders:
    1. C:
    2. cd C:\Program Files\HP\ALM\java
    3. set JAVA_HOME=C:\Program Files\HP\ALM\java
    4. psexec -s “%JAVA_HOME%\bin\jstack.exe” -l 12868 > C:\Temp\thread_dump.txt
      replace 4676 with the PID (Use Task Manager)
      replace C:\Temp\thread_dump.txt with the path where the thread dump should be exported to

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