Multiple ALM Test Run Scheduler processes exiting abruptly

I am working on a Dot Net Program(C#) that executes multiple ALM Test Sets on multiple machines simultaneously.
I am using "Scheduler" class for launching the execution that is part of OTAClient.dll.

I have taken help for the code from ALM C# OTA Help Document :
C# Run Test Instances in Test Set

I am able to launch execution (and it is getting finished) when 5-7 Test Run Schedulers are launched simultaneously.
But the Test Run Schedulers closes abruptly with following Test Specifications:
 1. Launched 20 Test Sets on 20 Machines (1-1 Mapping) : 20 Schedulers ran for 3 Hours and then all 20 exited abruptly

Things already tried:
 1. Already increased the system config to 8 CPU Cores and 16GB RAM on the machine running the Utility. Maximum RAM Usage at the time of process exiting was 2.5GB.
 2. No logs created for it in Event Viewer.

ALM Component Versions:

ALM Build Version = 12.50.32
OTA Client = 12.50.1287.0
Test Run Scheduler = 12.50.1287.0
Site Administration Client = 12.50.1287.0
Quality Center = 12.50.1287

What could be the issue of Test Run Scheduler exiting abruptly ?

3 Replies
Respected Contributor.
Respected Contributor.

Hello, in this lind of issues is necesary to collect extra information that the logs can gives us, you can follow the below steps, but if the issue persists, I'll recoment you to open a ticket with support.

clean client components.

1.Close all Internet Explorer windows

2. Run the uninstall utility tool: https://hpln.hpe.com/contentoffering/alm-client-cleanup-add-in


3. Please navigate to the %Temp% folder. Once in the “Temp” folder delete the “TD_80” subfolder. This is better known as the QC Cache. Like “Temporary Internet Files” this can be safely deleted. It will be recreated upon the next logon to Quality Center.

4. Use right click on Internet Explorer and select “Run as Administrator”

5. In the toolbar select Tools -> Internet Options

6. In the window that opened navigate to tab General

7. Under the section Browsing Settings click the History Button

8. In the window that opened click on the button View Files button

9. Delete all Temporally Internet Files

10. Temporarily disable UAC (User Account Control) and DEP (Data Execution Protection) settings. ALM has many known issues with these settings.


For more information on why it is important to disable UAC settings for QC components please follow this link: https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM1269825


Disable the Windows 7 UAC: Control Panel – User Accounts – Change User Account Control settings.

Disable DEP by running this command from a “Run as Admin” command prompt: bcdedit.exe /set {current} nx AlwaysOff

(NOTE: you can enable again this feature after our troubleshoot by running this command: bcdedit.exe /set {current} nx OptIn )


10. Reboot your client machine

11. Right click on Internet Explorer and select “Run as Administrator”

12. Open Quality Center main page (this will start to download the client components from the server)

13. Click on "Tools" page

14. Click on "HP ALM Client Registration"


Verify the required permission:




15. Click on "Register HP ALM”

16. Click on "Tools" page

17. Click on “HP ALM Connectivity”.

18. Download the connectivity add in and install it on the client machine.


Hi Jairo,

I have already tried the suggestions provided by you. Still facing the issue.

Issue is not with the launch of ALM Test Run Scheduler, but it is being exited abruptly after some time.

Could it be the large number of Test Run Schedulers [more than 20 having around 20 Tests in each] running simultaneously ?


Knowledge Partner Knowledge Partner
Knowledge Partner

You may also need to monitor the cpu and memory consumption on ALM application server. Did you notice any error messages in application server log files?

Especially for qcjavaservice.exe process on ALM server, see if test runs are failing when this process is reaching to crossing any particular value in memory & CPU consumption.

If that's the cause you may need to increase java heap size and RAM, # of cpu's on application server.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.