I recorded the Citrix script for our application. Before it worked fine yesterday when I replay. When I replay the script today while debugging it, I always got error like Citrix client does not perform the step as LR script requested. I forced to kill the citrix client and got error from LR as below
SharpDevelop Version : 4.1.0.0-00000000
.NET Version : 4.0.30319.18444
OS Version : Microsoft Windows NT 6.1.7601 Service Pack 1
Current culture : English (Canada) (en-CA)
Running under WOW6432, processor architecture: x86-64
Working Set Memory : 267412kb
GC Heap Memory : 43147kb
An unexpected error occurred.
Click ‘OK’ to close this message. You may be able to continue working,
but note that this workflow may cause the error to occur again.
Click ‘Details’ to display technical details on this error which may help
you solve the problem, or can be used when contacting customer support.
---- Post-error application state information:
Installed 3rd party AddIns: [UTT Configuratio UI 11.50.0.0], [Debug Pad Wrapper Extension addin for UTT 11.50.0.0], [UTT Debug Basic implementation addin for UTT 11.50.0.0], [UTT File Dialog 11.50.0.0], [UTT File Dialog 11.50.0.0], [HPUttIdeCommands 11.50.0.0], [UttBookmarkPad 11.50.0.0], [UttErrorListPad 11.50.0.0], [UttOutputPad 11.50.0.0], [UttTaskListPad 11.50.0.0], [Vugen.ConfigurationUI 11.50.0.0], [VuGen Debugger addin based on UT Debugger 11.50.0.0]
Workbench.ActiveContent: HP.LR.VuGen.ReplaySummary.ReplaySummaryViewContent
ProjectService.OpenSolution: [Solution: FileName=C:\Users\x173609\AppData\Local\Temp\LRStudio\6916\Untitled.ltsln, HasProjects=True, ReadOnly=False]
ProjectService.CurrentProject: [VuGenProject: CitrixICA]
---- Recent SharpDevelop log messages:
16:08:35.425 [23] ERROR - CloseAllClients error
--> Exception:
System.ServiceModel.CommunicationException: There was an error writing to the pipe: Unrecognized error 232 (0xe8). ---> System.IO.IOException: The write operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error writing to the pipe: Unrecognized error 232 (0xe8). ---> System.IO.PipeException: There was an error writing to the pipe: Unrecognized error 232 (0xe8).
at System.ServiceModel.Channels.PipeConnection.StartSyncWrite(Byte[] buffer, Int32 offset, Int32 size, Object& holder)
at System.ServiceModel.Channels.PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object& holder)
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.PipeConnection.WriteHelper(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, Object& holder)
at System.ServiceModel.Channels.PipeConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager)
at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
--- End of inner exception stack trace ---
at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.FramingDuplexSessionChannel.CloseOutputSessionCore(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.CloseOutputSession(TimeSpan timeout)
at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnClose(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnClose(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)
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 System.ServiceModel.ICommunicationObject.Close(TimeSpan timeout)
at System.ServiceModel.ClientBase`1.System.ServiceModel.ICommunicationObject.Close(TimeSpan timeout)
at System.ServiceModel.ClientBase`1.Close()
at HP.Utt.DebuggerDomain.Client.UttDebuggerDomainClientFactory.CloseAllClients() in e:\LT\UTT\win32_release\11.50.132.1\src\Infra\app\UttDebuggerDomainClient\UttDebuggerDomainClientFactory.cs:line 157
16:08:35.430 [6] ERROR - The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
--> Exception:
System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
Server stack trace:
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.IUttDebuggerDomain.StopDebugging()
at HP.Utt.DebuggerDomain.Client.UttDebuggerDomainClient.<StopDebugging>b__2f() in e:\LT\UTT\win32_release\11.50.132.1\src\Infra\app\UttDebuggerDomainClient\UttDebuggerDomainClient.cs:line 345
at HP.Utt.DebuggerDomain.Client.UttDebuggerDomainClient.NoFaultExceptionCall(Action action) in e:\LT\UTT\win32_release\11.50.132.1\src\Infra\app\UttDebuggerDomainClient\UttDebuggerDomainClient.cs:line 352
16:08:36.616 [1] ERROR - Unhandled WPF exception caught
--> Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
Server stack trace:
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 HP.Utt.Debugger.UttDebuggerImp.DebuggerCrash(Exception error) in e:\LT\UTT\win32_release\11.50.132.1\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 380
at HP.Utt.Debugger.UttDebuggerImp.<DebuggerCrash>b__4(Exception err) in e:\LT\UTT\win32_release\11.50.132.1\src\Infra\app\UttDebugger\UttDebuggerImp.cs:line 357
--- End of inner exception stack trace ---
Don't know why it pointed to e: driver. I even don't have e: driver.
Any thoughts? Thanks