Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49033

Issue with HPE Application Automation Tools plugin

    Details

    • Similar Issues:

      Description

      When using this plugin, I run a scenario, for some test cases in my scenario I get the desired results while for others I get 
      status : NoData
       

      whereas when I run this scenario in Load Runner, the scenario runs absolutely fine and results are displayed for all the tests in the scenario.

       

      Here are 2 examples of a expected result and no data result:

       
      Percentile : 90
      Full Name : Transaction Response Time (Percentile)
      Measurement : PercentileTRT
      Goal Value : 0.15
      Actual value : 0.126
      status : Passed
      ================================
      ================================
      Transaction Name : COLP_getLicense
      Percentile : 90
      Full Name : Transaction Response Time (Percentile)
      Measurement : PercentileTRT
      Goal Value : 0.06
      Actual value : 0
      status : NoData

        Attachments

        1. Screen Shot 2018-01-29 at 7.05.29 PM.png
          Screen Shot 2018-01-29 at 7.05.29 PM.png
          23 kB
        2. HTML.html
          0.5 kB
        3. jenkins_output.txt
          54 kB
        4. Session1.lra
          1 kB
        5. LRA.lra
          0.9 kB

          Activity

          Hide
          edwin_avedian Edwin Avedian added a comment -

          Rolando,

           

          The plugin version is 5.5 and LoadRunner version is 12.55.  I think I may have figured out part of the problem which is some scenarios weren't configured with 'Continue on Error' and that caused some of them to stop and fail and hence not have any data.

          Now for some of the projects we are getting the following errors in the logs which points to some kind of COM error.  If you could help us figure out how to resolve these then we should be able to get back on track:

           

          Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221164. [MsgId: MERR-108908]

          Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221008. [MsgId: MERR-108908]

           

           

          Thanks,
          Edwin

          Show
          edwin_avedian Edwin Avedian added a comment - Rolando,   The plugin version is 5.5 and LoadRunner version is 12.55.  I think I may have figured out part of the problem which is some scenarios weren't configured with 'Continue on Error' and that caused some of them to stop and fail and hence not have any data. Now for some of the projects we are getting the following errors in the logs which points to some kind of COM error.  If you could help us figure out how to resolve these then we should be able to get back on track:   Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221164. [MsgId: MERR-108908] Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221008. [MsgId: MERR-108908]     Thanks, Edwin
          Hide
          rolandomihaivlad Rolando-Mihai Vlad added a comment -

          Hello Edwin,

           

          Could you please check if only the scripts that are using WebServices protocol are failing ?

           

          Regards,

          Rolando

          Show
          rolandomihaivlad Rolando-Mihai Vlad added a comment - Hello Edwin,   Could you please check if only the scripts that are using WebServices protocol are failing ?   Regards, Rolando
          Hide
          edwin_avedian Edwin Avedian added a comment -

          Rolando,

           

          So I would say most that are failing are JAVA HTTP vusers.  Some of the JAVA vusers are also failing due to issues with not finding the correct version of Java.  We have a mix of C based HTTP and JAVA HTTP vusers And I would say most use WebServices protocol.

           

           

          Thanks,

          Edwin

           

          Show
          edwin_avedian Edwin Avedian added a comment - Rolando,   So I would say most that are failing are JAVA HTTP vusers.  Some of the JAVA vusers are also failing due to issues with not finding the correct version of Java.  We have a mix of C based HTTP and JAVA HTTP vusers And I would say most use WebServices protocol.     Thanks, Edwin  
          Hide
          rolandomihaivlad Rolando-Mihai Vlad added a comment -

          Hello Edwin,

          I will try to reproduce this issue and will keep you updated.

           

          Regards,

          Rolando

          Show
          rolandomihaivlad Rolando-Mihai Vlad added a comment - Hello Edwin, I will try to reproduce this issue and will keep you updated.   Regards, Rolando
          Hide
          rolandomihaivlad Rolando-Mihai Vlad added a comment - - edited

          Hello Edwin,

          Sorry for the delay. You might have some registry issues. Please register the LrWsNetClient.dll using the following commands:

          > cd <LR_Install_Directory>\bin

          > C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe LrWsNetClient.dll /regfile:LrWsNetClient.reg /codebase

           

          Regards,

          Rolando

          Show
          rolandomihaivlad Rolando-Mihai Vlad added a comment - - edited Hello Edwin, Sorry for the delay. You might have some registry issues. Please register the LrWsNetClient.dll using the following commands: > cd <LR_Install_Directory>\bin > C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe LrWsNetClient.dll /regfile:LrWsNetClient.reg /codebase   Regards, Rolando

            People

            • Assignee:
              rolandomihaivlad Rolando-Mihai Vlad
              Reporter:
              harry002300 Harsimrat Khattra
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: