Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. 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

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi All,
      we are facing the attached error when tried to execute the hp test scripts under hp ALM(Version11.0) from jenkins(Version1.476) using HP Application Automation Tools plugin(current Version). Referring solution from JENKINS-16464 issue(https://issues.jenkins-ci.org/browse/JENKINS-16464) I had also tried after downloading content from url(http://AlmServer:8080/qcbin/start_a.jsp?common=true) but same error repeated.

      Thanks in advance,
      any help is very much appreciated and
      please comment if any further info is needed on the issue,

      Update: Error is also occurring in our environment on ALM 11.52 since patch 4 was installed. It was working fine before installing patch 4. We have tested on Jenkins version 1.517 and version 1.581 with the HP Application Automation Tools plugin version 3.0.5.
      Additional information: The Event Viewer on the Jenkins server reports an application error with "wexectrl.exe", version 11.52.536.0. Please see attachment for further detail.

        Attachments

        1. cleanAlmClient.bat
          6 kB
        2. error.JPG
          error.JPG
          54 kB
        3. event viewer error.png
          event viewer error.png
          59 kB
        4. issue.png
          issue.png
          27 kB
        5. scheduler issue.7z
          67 kB
        6. step1.png
          step1.png
          50 kB
        7. step2.png
          step2.png
          16 kB
        8. step3.png
          step3.png
          25 kB
        9. step4.png
          step4.png
          57 kB
        10. step5done.png
          step5done.png
          13 kB

          Activity

          Hide
          amitbe Amit Bezalel added a comment -

          the clean script for alm client installations (removes all alm client installations from the machine)

          Show
          amitbe Amit Bezalel added a comment - the clean script for alm client installations (removes all alm client installations from the machine)
          Hide
          amitbe Amit Bezalel added a comment -

          You can use the script i attached to remove old alm client installations from the machine, then install the alm client by using commons=true or TDConnectivity_index.html (according to alm version).
          Regards,
          Amit.

          Show
          amitbe Amit Bezalel added a comment - You can use the script i attached to remove old alm client installations from the machine, then install the alm client by using commons=true or TDConnectivity_index.html (according to alm version). Regards, Amit.
          Hide
          marmac Marlene Macdonald added a comment -

          We have tried the clean and reinstall and no change, the same error is present.

          Show
          marmac Marlene Macdonald added a comment - We have tried the clean and reinstall and no change, the same error is present.
          Hide
          mark_z_davies Mark Davies added a comment -

          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.

          Show
          mark_z_davies Mark Davies added a comment - 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.
          Hide
          mholtz01 Mark Holtzclaw added a comment -

          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)

          Show
          mholtz01 Mark Holtzclaw added a comment - 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)
          Hide
          mark_z_davies Mark Davies added a comment -

          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.

          Show
          mark_z_davies Mark Davies added a comment - 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.
          Hide
          perefm Pere Felices added a comment - - edited

          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 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?

          Show
          perefm Pere Felices added a comment - - edited 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 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?
          Hide
          xiwenhpe xiwen zhao added a comment - - edited

          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

          Show
          xiwenhpe xiwen zhao added a comment - - edited 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
          Hide
          alisha Alisha Gakhar added a comment - - edited

          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

          Show
          alisha Alisha Gakhar added a comment - - edited 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
          Hide
          xiwenhpe xiwen zhao added a comment -

          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.

          Show
          xiwenhpe xiwen zhao added a comment - 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.
          Hide
          alisha Alisha Gakhar added a comment -

          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)

          Show
          alisha Alisha Gakhar added a comment - 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)
          Hide
          alisha Alisha Gakhar added a comment -

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

          Show
          alisha Alisha Gakhar added a comment - FYI I am using : Jenkins version 2.3 ALM and UFT version 12.53 hp-application-automation-tools-plugin version 5.0
          Hide
          tereshci Igor Tereshchuk added a comment -

          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.

          Show
          tereshci Igor Tereshchuk added a comment - 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.
          Hide
          tereshci Igor Tereshchuk added a comment -

          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.

          Show
          tereshci Igor Tereshchuk added a comment - 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.
          Hide
          alisha Alisha Gakhar added a comment -

          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.

          Show
          alisha Alisha Gakhar added a comment - 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.
          Hide
          karan_raka2003 Kiran Raka added a comment -

          Any updates ?

          I am unable to run Jenkin Job , getting 'unable to schedule.... error 

          1. Manual run from command prompt works ( HpToolsLauncher.exe -paramfile <file generated from plugin> from a command prompt (using the same user that is running the Jenkins service)

          2. ALM is registered and TD connectivity is already installed 

          Please note : on slave machine Jenkin is running as a service (tried running manually to troubleshoot but no luck )

          Thanks,

          Kiran 

           

          Show
          karan_raka2003 Kiran Raka added a comment - Any updates ? I am unable to run Jenkin Job , getting 'unable to schedule.... error  1. Manual run from command prompt works ( HpToolsLauncher.exe -paramfile <file generated from plugin> from a command prompt (using the same user that is running the Jenkins service) 2. ALM is registered and TD connectivity is already installed  Please note : on slave machine Jenkin is running as a service (tried running manually to troubleshoot but no luck ) Thanks, Kiran   
          Hide
          xiwenhpe xiwen zhao added a comment -

          Hi,

          We are not able to reproduce the problem locally, there is not much we can do at this stage.

          If you need to solve this issue please contact UFT support or ALM support to open a ticket, professional support team will follow up this issue. In this way your problem will have monitoring and tracking, in addition the case will be raised to higher level if it can not be solved in a short time. In another word it is guaranteed to be fixed by raising a support ticket.

          Meanwhile I will mark this issue as closed.

          Show
          xiwenhpe xiwen zhao added a comment - Hi, We are not able to reproduce the problem locally, there is not much we can do at this stage. If you need to solve this issue please contact UFT support or ALM support to open a ticket, professional support team will follow up this issue. In this way your problem will have monitoring and tracking, in addition the case will be raised to higher level if it can not be solved in a short time. In another word it is guaranteed to be fixed by raising a support ticket. Meanwhile I will mark this issue as closed.
          Hide
          xiwenhpe xiwen zhao added a comment -

          resolved, suggest customers to open UFT support ticket or ALM support ticket.

          Show
          xiwenhpe xiwen zhao added a comment - resolved, suggest customers to open UFT support ticket or ALM support ticket.
          Hide
          evanchen Evan Chen added a comment -

          Have anyone tried to run the test on the exact slave machine via ALM client on the machine directly? Wondering if there's something wrong with the ALM client.

          Show
          evanchen Evan Chen added a comment - Have anyone tried to run the test on the exact slave machine via ALM client on the machine directly? Wondering if there's something wrong with the ALM client.
          Hide
          karan_raka2003 Kiran Raka added a comment -

          I tried and it works if you run from HP ALM on the host machine but on otherhand if its Jenkin job fails with same error as above

          I am able to reproduce this issue everyday

          Show
          karan_raka2003 Kiran Raka added a comment - I tried and it works if you run from HP ALM on the host machine but on otherhand if its Jenkin job fails with same error as above I am able to reproduce this issue everyday
          Hide
          xiwenhpe xiwen zhao added a comment -
          1. You said it worked when you ran from host machine, so it only fails when you try to run on slave machine right?
          2. i dont quite understand the second part, what job fails? running from where(master or slave)? did you try to restart jenkins server? did you try to restart slave machine or terminate ALM related processes manually? Possibly ALM client process was not terminated correctly so it failed to create scheduler.

           

          Show
          xiwenhpe xiwen zhao added a comment - You said it worked when you ran from host machine, so it only fails when you try to run on slave machine right? i dont quite understand the second part, what job fails? running from where(master or slave)? did you try to restart jenkins server? did you try to restart slave machine or terminate ALM related processes manually? Possibly ALM client process was not terminated correctly so it failed to create scheduler.  

            People

            Assignee:
            xiwenhpe xiwen zhao
            Reporter:
            hvamsik Vamsi Hari
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: