[JIRA] (JENKINS-55968) Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html

2 views
Skip to first unread message

parimal.jaldawar@ril.com (JIRA)

unread,
Feb 5, 2019, 2:17:03 AM2/5/19
to jenkinsc...@googlegroups.com
Parimal Jaldawar created an issue
 
Jenkins / Bug JENKINS-55968
Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html
Issue Type: Bug Bug
Assignee: Daniel Gront
Attachments: Jenkins Issue.png
Components: hp-application-automation-tools-plugin
Created: 2019-02-05 07:16
Environment: Jenkins User ID: admin
Password: 3d17d3105ec342a4a6c117a3f7d465ce

Job: HPALM
Priority: Critical Critical
Reporter: Parimal Jaldawar

Started by user
admin
Building in workspace C:\Program Files (x86)\Jenkins\workspace\HPALM
[HPALM] $ "C:\Program Files (x86)\Jenkins\workspace\HPALM\HpToolsLauncher.exe" -paramfile props05022019123929426.txt
"Started..."
Timeout is set to: 30
Run mode is set to: RUN_LOCAL
============================================================================
Starting test set execution
Test set name: ENP_Execution_Release_Cycle_Jan_2019, Test set id: 512
Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form:
http://10.128.22.145:8080/qcbin//TDConnectivity_index.html
Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE
Recording test results
RunResultRecorder: didn't find any test results to record
Finished: FAILURE

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

parimal.jaldawar@ril.com (JIRA)

unread,
Feb 5, 2019, 2:19:02 AM2/5/19
to jenkinsc...@googlegroups.com

parimal.jaldawar@ril.com (JIRA)

unread,
Feb 5, 2019, 2:34:02 AM2/5/19
to jenkinsc...@googlegroups.com
Parimal Jaldawar updated an issue
 
Change By: Parimal Jaldawar
Environment:

Jenkins User ID: admin
Password: 3d17d3105ec342a4a6c117a3f7d465ce

Job: HPALM
Dear sir, 

we are trying to execute the  Microfocus ALM test with the help of jenkins.

I have shared the Jenkins credentials with you.

 

Jenkins Version: 2.163

HP ALM version: 12.50

Env: RIL domain

Appreciate your help to resolve the problem.

 

Started by user
[admin|http://localhost:8080/user/admin]

Building in workspace C:\Program Files (x86)\Jenkins\workspace\HPALM
[HPALM] $ "C:\Program Files (x86)\Jenkins\workspace\HPALM\HpToolsLauncher.exe" -paramfile props05022019123929426.txt
"Started..."
Timeout is set to: 30
Run mode is set to: RUN_LOCAL
============================================================================
Starting test set execution
Test set name: ENP_Execution_Release_Cycle_Jan_2019, Test set id: 512
Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form:

Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE
Recording test results
RunResultRecorder: didn't find any test results to record
Finished: FAILURE

t.a.dautzenberg@gmail.com (JIRA)

unread,
Jul 19, 2019, 3:36:02 AM7/19/19
to jenkinsc...@googlegroups.com
Thomas Dautzenberg commented on Bug JENKINS-55968
 
Re: Facing Error Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://10.128.22.145:8080/qcbin//TDConnectivity_index.html

Hi,

 

I don't know if this will be the solution for everyone, but I was facing the same issue until I tried the following.

 

First, install a version of TDconnectivity that does not match with the ALM Version installed (I used this one https://almcgo.saas.hpe.com/qcbin/TDConnectivity_index.html)

When trying to run your UFT Tests from jenkins, you will get an error about version incompatibility

After that install the correct version for your ALM using the link provided when you got the first error

 

Now, try again running tests from Jenkins.

 

This worked for me

 

 

Reply all
Reply to author
Forward
0 new messages