-
Bug
-
Resolution: Not A Defect
-
Major
-
LR 12.53 Patch 4, Jenkins v1.651.2, HP Plugin v4.0
When we run tests via Jenkins we see that the build is still running long after the scenario ends. When we log into the LoadRunner Controller/Jenkins Slave we see that there is a window open indicating that The HP LoadRunner Controller has stopped working. In order for the Jenkins build to completely stop I have to kill that window (WerFault.exe) Jenkins's reports:
Error: The Controller is still running...
Error: Test FAILED. 1 errors occured during scenario execution.
Error: Cannot close Controller gracefully, exception details:
Error: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
Error: at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at HP.LoadRunner.Interop.Wlrun.LrEngineClass.CloseController()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.closeController()
Error: killing Controller process
[JENKINS-42403] HP LoadRunner Controller often fails to close when running from Jenkins
shadruzzaman ..
added a comment - I am using HP application automation tools plugin 5.1 I'm on it - please try with v5 or set scenario timeout in the meanwhile as it should solve this.
Perftst1 SQAD
added a comment - With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process). So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window. Found the link below and we will try to disable. If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e. C:\>taskkill /IM WerFault.exe /F ) when the controller crash even happens.
http://windows-exe-errors.com/how-to-disable-werfault-exe-in-windows/
Perftst1 SQAD
added a comment - With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process). So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window. Found the link below and we will try to disable. If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e. C:\>taskkill /IM WerFault.exe /F ) when the controller crash even happens.
http://windows-exe-errors.com/how-to-disable-werfault-exe-in-windows/ Perftst1 SQAD
added a comment - Yafim - In the v5.1 plugin which we're about to download to test, will we be able to see the Controller GUI execute? I see this problem was commented on in JENKINS-28075 and was wondering if that toggle option is available in the plugin version 5.1?
We absolutely need to see the LR Controller GUI during the Jenkins Build execution.
Perftst1 SQAD
added a comment - Yafim - In the v5.1 plugin which we're about to download to test, will we be able to see the Controller GUI execute? I see this problem was commented on in JENKINS-28075 and was wondering if that toggle option is available in the plugin version 5.1?
We absolutely need to see the LR Controller GUI during the Jenkins Build execution. On feature - not yet. In our backlog. To maintain the clarity here - please keep this to our google group or to the specific JIRA issue / feature.
On the issue - please try by downgrading to v5 or setting the timeout and scenario execution timeout - and it should solve this.
shadru please reopen if you still encounter this after upgrading the plugin.
shadruzzaman ..
added a comment - @Yafim Kazak: Thanks for the update. I will install the updated plugin and come back to you if still I will get the same issue
shadruzzaman ..
added a comment - @Yafim Kazak: Thanks for the update. I will install the updated plugin and come back to you if still I will get the same issue 
syed basha
added a comment - With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process). So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window. Found the link below and we will try to disable. If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e. C:\>taskkill /IM WerFault.exe /F ) when the controller crash even happens. http://www.techealthexperts.com/service-host-local-system-network-restricted-10
syed basha
added a comment - With regards to our particular issue we notice that this is due to the WerFault.exe (Window Error Reporting process). So when the Controller does not close gracefully, which we don't know why, Windows Error Reporting will present that popup window. Found the link below and we will try to disable. If that doesn't work we'll probably have to write a script that runs on the Controller windows machine to kill the task (i.e. C:\>taskkill /IM WerFault.exe /F ) when the controller crash even happens. http://www.techealthexperts.com/service-host-local-system-network-restricted-10 
Hi which plugin version do you use? is it v4 as stated above?