.NET WCF Proxy error while not running Fiddler

[Gunarathinam]

Hi Team,

We installed Fiddler to troubleshoot the web request generated from Windows Service(developed using .NET WCF).All fine for us from debugging point of view.

Moment we close Fiddler, the windows service stopped working by logging below error from .NET WCF service

Error Message: There was no endpoint listening at https://xyz.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details., StackTrace - 
Server stack trace: 
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   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)

 

We need to understand, why services works fine when fiddler is running in background and not if it closed?

Any settings we missing? This issue is on Windows Server 2012 R2 Server. 

 

Regards,

Guna. 

[Tsviatko Yovtchev]

Hi,

How did you set up Fiddler to be the proxy of your WCF service? Did you change web.config/machine.config? Did you revert these changes after closing Fiddler? Did you restart the service after reverting the changes?

Regards,
Tsviatko Yovtchev
Telerik