[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html

78 views
Skip to first unread message

mark.davies@fonterra.com (JIRA)

unread,
Oct 28, 2015, 12:20:01 AM10/28/15
to jenkinsc...@googlegroups.com
Mark Davies commented on Bug JENKINS-19374
 
Re: issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html

We are also experiencing exactly the same issue. Have removed all instances of ALM Client from the machine, then registered the client again with http://<almserver>:8080/qcbin/start_a.jsp?Common=true.

I note that if i launch the HpToolsLauncher.exe -paramfile <file generated from plugin> from a command prompt (using the same user that is running the Jenkins service) it executes successfully and records the run in ALM. This would suggest the ALM client is working ok. Perhaps the issue is in the way the plugin is spawning child processes under Jenkins.

Any updates or suggestions on this issue would be appreciated.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

Mark.Holtzclaw@sprint.com (JIRA)

unread,
Jan 11, 2016, 9:47:02 AM1/11/16
to jenkinsc...@googlegroups.com

Adding more information that will hopefully help in leading to a solution. Our site is experiencing the same issue, but some additional details that we have noticed:

  • We cannot run the job utilizing the plugin using a thread on the jenkins master; it has to be done via a slave
  • If we start the slave not as a service (ie, logged in as a user and starting the slave manually), the plugin works

Although we can sucessfully use the plugin, it's not practical to have our slaves started manually (not as a service)

mark.davies@fonterra.com (JIRA)

unread,
Jan 11, 2016, 5:50:01 PM1/11/16
to jenkinsc...@googlegroups.com

I agree Mark H. This is our findings as well. We are using a work around to starting the slave as a service. We are using the Windows Task scheduler to start the JNLP slave at windows startup so at least if the machine restarts the Slave will restart as well. Not ideal but got us going until the Plugin owners get a chance to find a solution to running as a service.

kazak@hpe.com (JIRA)

unread,
Sep 27, 2016, 2:29:04 AM9/27/16
to jenkinsc...@googlegroups.com
Yafim Kazak updated an issue
 
Jenkins / Bug JENKINS-19374
Change By: Yafim Kazak
Labels: ALM
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

kazak@hpe.com (JIRA)

unread,
Sep 27, 2016, 2:29:04 AM9/27/16
to jenkinsc...@googlegroups.com
Yafim Kazak assigned an issue to Roy Lu
Change By: Yafim Kazak
Assignee: Amit Bezalel Roy Lu

li.lu@hpe.com (JIRA)

unread,
Oct 31, 2016, 4:58:04 AM10/31/16
to jenkinsc...@googlegroups.com
Roy Lu assigned an issue to xiwen zhao
Change By: Roy Lu
Assignee: Roy Lu xiwen zhao

xpherezn@gmail.com (JIRA)

unread,
Nov 23, 2016, 12:46:01 PM11/23/16
to jenkinsc...@googlegroups.com
Pere Felices commented on Bug JENKINS-19374
 
Re: issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html

Hi,
We have ALM 12.30 and UFT 12.51 and none of the solutions are working, we have tried to execute on localhost, execute in remote (as a service and as JNPL), reinstalling the TD Connect plugin and re-registering the ALM client, we have tried to clean previosu installations too.
But none of the solutions are working.

Surprisingly, if we call manually the tool from the command line seems to work (calling directly: HpToolsLauncher.exe -paramfile propsXXXXXXXXXXX.txt"), but when calling the task from Jenkins, it fails.

Could be some kind of permissions issue?

xpherezn@gmail.com (JIRA)

unread,
Nov 23, 2016, 12:46:03 PM11/23/16
to jenkinsc...@googlegroups.com
Pere Felices edited a comment on Bug JENKINS-19374
Hi,
We have ALM 12.30 and UFT 12.51 and none of the solutions are working, we have tried to execute on localhost, execute in remote (as a service and as JNPL), reinstalling the TD Connect plugin and re-registering the ALM client, we have tried to clean previosu previous installations too.

But none of the solutions are working.

Surprisingly, if we call manually the tool from the command line seems to work (calling directly: HpToolsLauncher.exe -paramfile propsXXXXXXXXXXX.txt"), but when calling the task from Jenkins, it fails.

Could be some kind of permissions issue?

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 3:56:02 AM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao started work on Bug JENKINS-19374
 
Change By: xiwen zhao
Status: Open In Progress

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 3:56:02 AM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao updated an issue
 
Change By: xiwen zhao
Priority: Blocker Critical

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 10:36:01 PM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao commented on Bug JENKINS-19374
 
Re: issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html

Environment setups:
Jenkins 1.642.4
hp-application-automation-tools-plugin 5.0.1-beta-SNAPSHOT
ALM 12.01
UFT 14.0 build 1708
Win10 64 EN (Master)
Win10 64 EN (Slave)

The problem is caused by ALM Client registration, users need to register ALM client manually.
how to solve this problem:
1. right click Internet Explorer icon on your desktop
2. select "Run as Administrator"
3. navigate to your ALM server
4. click "Tools"
5. click "HP ALM Client Registration"
6. click "Register HP ALM"
7. wait for the process to complete, close the window
Now you should be able to run test on ALM.
Please see attached screenshots for details

However, I tried to config JNLP to run as windows service, it works fine just as I start JNLP manually.

Before ALM client is manually registered, neither run from Jenkins or Run from command prompt by typing "HpToolsLauncher.exe -paramfile propsxxxxxxxxx.txt" would work. After registering ALM client by the steps mentioned above, both command prompt and run from Jenkins worked fine.

If the problem still exists, please download the 7z package attached and replace all three exe files on your computer accordingly.
Run the test twice to collect logs.
1. run from Jenkins, collect Jenkins console output, this run should fail
2. run from command prompt, collect console output in command window, this run should success.
attach the logs or screenshots to this defect so i can investigate further.

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 10:37:01 PM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao updated an issue
Change By: xiwen zhao
Attachment: step1.png
Attachment: step2.png
Attachment: step3.png
Attachment: step4.png
Attachment: step5done.png
Attachment: scheduler issue.7z

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 10:55:02 PM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao edited a comment on Bug JENKINS-19374
Environment setups:
Jenkins 1.642.4
hp-application-automation-tools-plugin 5.0.1-beta-SNAPSHOT
ALM 12.01
UFT 14.0 build 1708
Win10 64 EN (Master)
Win10 64 EN (Slave)

The problem is caused by ALM Client registration, users need to register ALM client manually.
how to solve this problem:
    1. right click Internet Explorer icon on your desktop
    2. select "Run as Administrator"
    3. navigate to your ALM server
    4. click "Tools"
    5. click "HP ALM Client Registration"
    6. click "Register HP ALM"
    7. wait for the process to complete, close the window
Now you should be able to run test on ALM.
Please see attached screenshots for details

However, I tried to config JNLP to run as windows service, it works fine just as I start JNLP manually.

Before ALM client is manually registered, neither run from Jenkins or Run from command prompt by typing "HpToolsLauncher.exe -paramfile propsxxxxxxxxx.txt" would work. After registering ALM client by the steps mentioned above, both command prompt and run from Jenkins worked fine.

If the problem still exists, please download the 7z package attached and replace all three exe files on your computer accordingly.
 Run the test twice to collect logs.
1. run from Jenkins, collect Jenkins console output, this run should fail . check if jenkinsslave service is running.
2. run from command prompt, collect console output in command window, this run should success. check if jenkinsslave service is running.
attach the logs or screenshots to this defect , and specify if the jenkinsslave service is running, so i can investigate further. Thank you.

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 3, 2017, 10:57:03 PM1/3/17
to jenkinsc...@googlegroups.com
xiwen zhao edited a comment on Bug JENKINS-19374
Environment setups:
Jenkins 1.642.4
hp-application-automation-tools-plugin 5.0.1-beta-SNAPSHOT
ALM 12.01
UFT 14.0 build 1708
Win10 64 EN (Master)
Win10 64 EN (Slave)

The problem is caused by ALM Client registration, users need to register ALM client manually.
how to solve this problem:
    1. right click Internet Explorer icon on your desktop
    2. select "Run as Administrator"
    3. navigate to your ALM server
    4. click "Tools"
    5. click "HP ALM Client Registration"
    6. click "Register HP ALM"
    7. wait for the process to complete, close the window
Now you should be able to run test on ALM.
Please see attached screenshots for details

However, I tried to config JNLP to run as windows service, it works fine just as I start JNLP manually.

Before ALM client is manually registered, neither run from Jenkins or Run from command prompt by typing "HpToolsLauncher.exe -paramfile propsxxxxxxxxx.txt" would work. After registering ALM client by the steps mentioned above, both command prompt and run from Jenkins worked fine.

If the problem still exists, please download the 7z package attached and replace all three exe files on your computer accordingly.
1. run from Jenkins, collect Jenkins console output, this run should fail. check if jenkinsslave service is running.

2. run from command prompt, collect console output in command window, this run should success. check if jenkinsslave service is running.
attach the logs or screenshots to this defect, and specify if the jenkinsslave service is running, so i can investigate further. Thank you.

duplicate defects: JENKINS-40736 JENKINS-16464 JENKINS-29957

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 4, 2017, 9:27:03 PM1/4/17
to jenkinsc...@googlegroups.com
xiwen zhao resolved as Cannot Reproduce
 
Change By: xiwen zhao
Status: In Progress Resolved
Resolution: Cannot Reproduce

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 4:41:02 AM1/24/17
to jenkinsc...@googlegroups.com
Alisha Gakhar updated an issue
Change By: Alisha Gakhar
Attachment: error.JPG

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 4:42:01 AM1/24/17
to jenkinsc...@googlegroups.com

xiwen.zhao@hpe.com (JIRA)

unread,
Jan 24, 2017, 5:00:01 AM1/24/17
to jenkinsc...@googlegroups.com

Hi Gakhar,

If the problem still exists, please download the 7z package attached and replace all three exe files on your computer accordingly.
1. run from Jenkins, collect Jenkins console output, this run should fail. check if jenkinsslave service is running.
2. run from command prompt, collect console output in command window, this run should success. check if jenkinsslave service is running.
attach the logs or screenshots to this defect, and specify if the jenkinsslave service is running, so i can investigate further. Thank you.

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 5:31:03 AM1/24/17
to jenkinsc...@googlegroups.com
Alisha Gakhar edited a comment on Bug JENKINS-19374
Following all the above steps ,still facing an issue both from Jenkins and command prompt with error message: (error.png)
Unable to acquire lock on file c:\jenkins\workspace\*JOBNAME*\. Could not find a part of the path 'c:\jenkins\workspace\*JOBNAME*\'.
Problem while running TestSet: Exception from HRESULT: 0x80040459

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 5:35:04 AM1/24/17
to jenkinsc...@googlegroups.com

Hi Zhao

I did replace the three exe files with the attached files and tried running from Jenkins as well as command prompt using -HpToolsLauncher.exe -paramfile propsxxxxxxxxx.txt but I am receiving different error with message:
Unable to acquire lock on file c:\jenkins\workspace*JOBNAME*\. Could not find a part of the path 'c:\jenkins\workspace*JOBNAME*\'.


Problem while running TestSet: Exception from HRESULT: 0x80040459

You may check the screenshot(error.jpg)

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 5:57:02 AM1/24/17
to jenkinsc...@googlegroups.com

FYI
I am using :
Jenkins version 2.3
ALM and UFT version 12.53
hp-application-automation-tools-plugin version 5.0

igor.tereshchuk@hpe.com (JIRA)

unread,
Jan 24, 2017, 6:13:03 AM1/24/17
to jenkinsc...@googlegroups.com

such error could be when ALM client is not registered in common mode or ALM client was registered with higher version then actual ALM is.
So my suggestions take clean environment download only on of the available ALM version in common mode. Try run job.

igor.tereshchuk@hpe.com (JIRA)

unread,
Jan 24, 2017, 7:27:02 AM1/24/17
to jenkinsc...@googlegroups.com

I've checked execution test with Jenkins 2.19.1 , Jenkins Plugin version 5.0. UFT 12.52 b 6851 + ALM11.52 P9. Works fine.

alisha.gak@gmail.com (JIRA)

unread,
Jan 24, 2017, 10:48:03 AM1/24/17
to jenkinsc...@googlegroups.com

I am able to resolve my issue:


Unable to acquire lock on file c:\jenkins\workspace*JOBNAME*\. Could not find a part of the path 'c:\jenkins\workspace*JOBNAME*\'.
Problem while running TestSet: Exception from HRESULT: 0x80040459

Prior to resolution,the configuration of the job was set to 'run on planned host'.
I changed it to 'run on local' and I was able to successfully run my test set on slave machine.
Reply all
Reply to author
Forward
0 new messages