loadrunner I upgraded my PC to 64 bit,since then...

  • Thread starter Avinash K Devanga
  • Start date
  • perf-test.com need your contributions to build up a strong repository of performance engineering resources.

A

Avinash K Devanga

Guest
I upgraded my PC to 64 bit,since then LoadRunner 12 is giving this error after pressing play or compile button. JDK 7 is installed. I tried reinstalling LoadRunner and java.Nothing is working.Any help is appreciated.
 
It must be something related to JDK parameters. Also please check if any errors appear in VuGen log in %temp% folder.
 
Igor MarkovI am getting same error for web scripts too. I tried it on multiple 64 bit pcs on windows 7,all are giving same error. Windows 8 64 bit is working fine.
 
This is the error log message. 2014-10-09 18:14:53,518 ExceptionFormatter [ 1] ERROR - System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.pipe://localhost/session_id=10445312/UttDebuggerDomainDebuggers that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HP.Utt.DebuggerDomain.Interface.IUttDebuggerDomainDebuggers.get_Count() at HP.Utt.Debugger.UttDebuggerImp.GetExternalDebuggerInfo(String debuggerName) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 143 at HP.Utt.Debugger.UttDebuggerImp.Initialize(String debuggerName) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 70 at HP.Utt.Debugger.UttDebuggerImp.Compile(String command) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 1389 at HP.LR.Vugen.DebuggerBackend.VugenDebuggerUtilities.Compile(String usrFileName, String resultName, String configFileName, Object extraData) in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\BackEnd\Current\Debugger\HP.LR.Vugen.DebuggerBackend\VugenDebuggerUtilities.cs:line 284 at HP.LR.Vugen.FrontEnd.DebuggerAddin.Gui.ReplayOperations.Compile(Boolean resetDebugCommandProgress) in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\FrontEnd\Current\CoreAddins\VuGenDebugger\Gui\ReplayOperations.cs:line 34 at HP.LR.Vugen.FrontEnd.DebuggerAddin.Gui.ReplayOperations.<>c__DisplayClass7.b__5() in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\FrontEnd\Current\CoreAddins\VuGenDebugger\Gui\ReplayOperations.cs:line 57 at System.Threading.Tasks.Task`1.InvokeFuture(Object futureAsObj) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute() 2014-10-09 18:14:53,527 VUGEN [ 1] ERROR - There was no endpoint listening at net.pipe://localhost/session_id=10445312/UttDebuggerDomainDebuggers that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Exception Data: There was no endpoint listening at net.pipe://localhost/session_id=10445312/UttDebuggerDomainDebuggers that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Stack Trace: Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper) at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout) at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at HP.Utt.DebuggerDomain.Interface.IUttDebuggerDomainDebuggers.get_Count() at HP.Utt.Debugger.UttDebuggerImp.GetExternalDebuggerInfo(String debuggerName) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 143 at HP.Utt.Debugger.UttDebuggerImp.Initialize(String debuggerName) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 70 at HP.Utt.Debugger.UttDebuggerImp.Compile(String command) in e:\LT\UTT\win32_release\12.01.1601.10\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 1389 at HP.LR.Vugen.DebuggerBackend.VugenDebuggerUtilities.Compile(String usrFileName, String resultName, String configFileName, Object extraData) in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\BackEnd\Current\Debugger\HP.LR.Vugen.DebuggerBackend\VugenDebuggerUtilities.cs:line 284 at HP.LR.Vugen.FrontEnd.DebuggerAddin.Gui.ReplayOperations.Compile(Boolean resetDebugCommandProgress) in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\FrontEnd\Current\CoreAddins\VuGenDebugger\Gui\ReplayOperations.cs:line 34 at HP.LR.Vugen.FrontEnd.DebuggerAddin.Gui.ReplayOperations.<>c__DisplayClass7.b__5() in e:\LT\LT-LR\win32_release\12.01.2079.0_clean\app\VuGen\FrontEnd\Current\CoreAddins\VuGenDebugger\Gui\ReplayOperations.cs:line 57 at System.Threading.Tasks.Task`1.InvokeFuture(Object futureAsObj) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute() 2014-10-09 18:14:53,528 SharpDevelop [ 1] ERROR - An error has occurred.
 
This is not a 64bit issue, but rather other environment problem. According to log, when VuGen runs a scripts it cannot execute/connect to debugger process. Are you running VuGen as admin user? If not, can you try?
 
Avinash K Devanga, what version of LR do you have? Do you know if the non-admin user, you have used, has special policies set? Anything related to inter-process communication or networking? I am asking because LR is built and tested to work with non-admin user, but naturally not all settings can be fully covered.
 
Igor Markov we cannot run 11.5 as non-admin either. But it could be due to company's security settings.
 
Megan Smith Shelton, the non-admin support in LR was gradually added in 11.51-11.52-12.00 releases. In 11.52 release VuGen and Analysis applications can work under non-admin user, and in 12.00 all LR software works with non-admin user (except for specific cases where admin permissions really needed, as listed in readme/docs). If there is something specific that doesn't work - let me know.
 
Revert back windows updates. This is the most commonly happening with LR 12. If you are inside of a firewall, better turn of windows updates.
 
Kishore Devisetti, apart from the installation, are you running VuGen as admin user? What exactly LR version are you using?