Highlighted
Absent Member.
Absent Member.
2236 views

The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

We're trying to invoke a LR scenario from Jenkins via pipeline code using the loadRunnerTest step, but when the test completes there is an error right after the 'closing controller' step. The error says 'RPC server is unavailable'.. logs copied below for the relevant section.

there are no remote load generators used here. And we're on LR 12.5. Anyone else seen this before? 

 

Analyzing results...
closing Controller
Unhandled Exception: System.Runtime.InteropServices.COMException: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
   at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
   at HP.LoadRunner.Interop.Wlrun.LrEngineClass.get_Scenario()
   at HpToolsLauncher.TestRunners.PerformanceTestRunner.updateVuserStatus()
   at HpToolsLauncher.TestRunners.PerformanceTestRunner.isFinished()
   at HpToolsLauncher.TestRunners.PerformanceTestRunner.DoTask(Object state)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
Recording test results
None of the test reports contained any result
RunResultRecorder: didn't find any test results to record

 

0 Likes
8 Replies
Highlighted
Absent Member.
Absent Member.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

Was able to reproduce error via command line execution of HptoolsLauncher.exe.. the full error message from event logs is copied below.

Faulting application name: HpToolsLauncher.exe, version: 1.0.0.0, time stamp: 0x58593c1c
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18007, time stamp: 0x55c4bcfc
Exception code: 0xe0434352
Fault offset: 0x00015b68
Faulting process id: 0x13ac
Faulting application start time: 0x01d2a4d5700f96c6
Faulting application path: C:\Jenkins\workspace\ion_feature-US206554.d4v0vh-GA2M3ZHGFNCQ3F7UGSWFPEDWDDWRPCI5WYUTNUBQCFFDFQ6IFUZA\HpToolsLauncher.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: a4d63f25-10c9-11e7-80c4-b432a410729c
Faulting package full name:
Faulting package-relative application ID:

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

.NET stack trace:

Application: HpToolsLauncher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.RuntimeType.ForwardCallToInvokeMember(System.String, System.Reflection.BindingFlags, System.Object, Int32[], System.Runtime.Remoting.Proxies.MessageData ByRef)
at HP.LoadRunner.Interop.Wlrun.LrEngineClass.get_Scenario()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.updateVuserStatus()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.isFinished()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.DoTask(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

 

0 Likes
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

Hi,

Please create this issue in our plugin issue management system.

Reachable from our main site- by clicking "open issues"

HPE Jenkins plugin main site / wiki page

Or using the following direct link:

Jenkins plugins issue reporting / feature suggestion system

 

Please share the following on the ticket so we could diagnose the issue -

  1. Jenkins master OS and Jenkins version
  2. Jenkins slave OS and Jenkins version
  3. HPE Jenkins plugin version (if it's not at least v5 - please update and see if the issue is reproduced)
  4. LoadRunner version including any installed patches.
  5. Does the Jenkins slave runs with special Jenkins user privileges as suggested
  6. Job configuration files:

<Jenkins master folder>\jobs\<Job name>\config.xml

<Jenkins master folder>\jobs\<Job name>\build\<bad build number> (whole folder - so we can analyze LR files as well).

 

[If you don't want to wish to upload configuration files to the issue system - please update and we will contact you to receive them privately]

 

 

 

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

The issue went away when we recreated the scenario.. so not sure if there was something in the scenario file causing this unhandled exception.

Also, noticed that the LRanalysisLauncher has a timeout it works with, but can't find out where this can be configured. Is this set to match the test duration or scenario timeout now? That can cause trouble for small tests <5 minutes, since scenario timeout is automatically set to 5 minutes too.

Controller closed
calling analysis report generator
executing Analysis launcher with arguments : [deleted values for lrr/lra/html file paths]
time for analysis: 00::00:10:00 ---> this value always matches the scenario timeout
starting analysis launcher
creating analysis COM object
creating analysis session
                           
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

I think I found the reason for the unhandled exception with the HP plugin. When the scenario has any script groups that are in disabled state (enabled=0 in the lrs file) the HpToolsLauncher fails with this error:

Application: HpToolsLauncher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
Stack:
at System.RuntimeType.ForwardCallToInvokeMember(System.String, System.Reflection.BindingFlags, System.Object, Int32[], System.Runtime.Remoting.Proxies.MessageData ByRef)
at HP.LoadRunner.Interop.Wlrun.ILrScenario.GetVusersCount(Int32)
at HpToolsLauncher.TestRunners.PerformanceTestRunner.updateVuserStatus()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.isFinished()
at HpToolsLauncher.TestRunners.PerformanceTestRunner.DoTask(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

 

---

Should the plugin code be updated to handle disabled script groups in a scenario like the manual execution allows it?

0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

Hi Aishwarya,

I have also seen the "RPC server is unavailable" message when confiuging LoadRunner with Jenkins and not with jmeter and Gatling.

I simply restarted the machine whenever i got the RPC cinnection failed message. It worked withour any issue thereafter.

 

Regards,

Raghul M

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

Good catch.

Can you please report this defect in  the plugin group on Google? https://groups.google.com/forum/#!forum/hp-application-automation-tools-plugin. The plugin owner reviews and addresses all posts.

I will forward this post to him in any case.

Thanks,

Shlomi

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: The RPC server is unavailable - exception seen during Jenkins pipeline execution of HP LR plugin

 

Continue to Yafim reply above, please share the following on the ticket so we could diagnose the issue -

  1. Jenkins master OS and Jenkins version
  2. Jenkins slave OS and Jenkins version
  3. HPE Jenkins plugin version (if it's not at least v5 - please update and see if the issue is reproduced)
  4. LoadRunner version including any installed patches.
  5. Does the Jenkins slave runs with special Jenkins user privileges as suggested
  6. Job configuration files:

<Jenkins master folder>\jobs\<Job name>\config.xml

<Jenkins master folder>\jobs\<Job name>\build\<bad build number> (whole folder - so we can analyze LR files as well).

Thanks,

Dikla

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.