-
Bug
-
Resolution: Unresolved
-
Critical
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
[JENKINS-49033] Issue with HPE Application Automation Tools plugin
Rolando-Mihai Vlad
added a comment - Hello Harsimrat,
Can you please provide two .lra files for the same scenario one time by running your scenario on LR controller and analyzing the result with analysis and another time by using the jenkins plugin.
Best regards,
Vlad Rolando-Mihai
Rolando-Mihai Vlad
added a comment - Hello Harsimrat,
Can you please provide two .lra files for the same scenario one time by running your scenario on LR controller and analyzing the result with analysis and another time by using the jenkins plugin.
Best regards,
Vlad Rolando-Mihai No response from the reporter, If the problem arises again please reopen and provide the requested files
Edwin Avedian
added a comment - rolandomihaivlad, I apologize for the long delay. I am picking up this issue from my colleague Harsimrat and I am attaching the 2 .lra files requested, LRA.lra from the Jenkins run and Session1.lra from the LR controller run. What I notice is that NoData is showing up for missing transactions when run from Jenkins. The question is why some transactions are missing when the scenario is run using Jenkins plugin.
Edwin Avedian
added a comment - rolandomihaivlad , I apologize for the long delay. I am picking up this issue from my colleague Harsimrat and I am attaching the 2 .lra files requested, LRA.lra from the Jenkins run and Session1.lra from the LR controller run. What I notice is that NoData is showing up for missing transactions when run from Jenkins. The question is why some transactions are missing when the scenario is run using Jenkins plugin.
Session1.lra
LRA.lra Rolando-Mihai Vlad
added a comment - Hello Edwin,
I forgot to ask you to add the LoadRunner version and plugin version. Also, please add the whole LRA folder for both cases.
Regards,
Rolando
Rolando-Mihai Vlad
added a comment - Hello Edwin,
I forgot to ask you to add the LoadRunner version and plugin version. Also, please add the whole LRA folder for both cases.
Regards,
Rolando 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
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 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
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 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
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
Rolando-Mihai Vlad
added a comment - Hello Edwin,
I will try to reproduce this issue and will keep you updated.
Regards,
Rolando
Rolando-Mihai Vlad
added a comment - Hello Edwin,
I will try to reproduce this issue and will keep you updated.
Regards,
Rolando 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
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 
Hi yafim_kazak, any updates on this?