WCF Service is not accessible after removing Network Cable RRS feed

  • Question

  • Hi,

    On my machine after removing network cable i am not able to call WCF Services. Not able to find any application exception. But below are the exceptions which i got from Event viewer - System.

    Error 1

    The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has succesfully processed. If you do not see a success message for several hours, then contact your administrator.

    Error 2

    An error occurred while parsing the net.pipe binding '*' of the site '1', thus the protocol is disabled for the site temporarily. See the exception message for more details.
     Binding: net.pipe:*
     Source: System.ServiceModel.Activation.ListenerAdapter/4032828
     Exception: System.UriFormatException: The protocol binding '*' is not valid for 'net.pipe'.  This might be because the port number is out of range.
       at System.ServiceModel.Channels.BaseUriWithWildcard..ctor(String protocol, Int32 defaultPort, String binding, Int32 segmentCount, String path)
       at System.ServiceModel.Channels.BaseUriWithWildcard.CreateUri(String protocol, String binding, String path)
       at System.ServiceModel.Activation.ListenerAdapter.RegisterBindings(IActivatedMessageQueue queue, Int32 siteId, String[] bindings, String path)
     Process Name: SMSvcHost
     Process ID: 5276

    Error 3

    An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
     ID: 5552
     Source: System.ServiceModel.Activation.TcpWorkerProcess/2061578
     Exception: System.ServiceModel.FaultException: The client was unable to process the callback request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from CallbackBehaviorAttribute or from the <clientDebug> configuration behavior) on the client in order to send the exception information back to the server, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the client trace logs.

    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
      Process Name: SMSvcHost
     Process ID: 2600

    Can you help us to find the reason.?

    Friday, December 2, 2016 9:32 AM

All replies

  • The WCF service has nothing to do with what is happening on the WCF client side when the client can't connect to the WCF service.

    The link talks about the try/catch that should be implemented when the client side code makes the call to a WCF service. You should ignore about the talk on the subject about, "Advoiding Problems with the Using statement", but rather,  you try to implement the try/catch pattern and exception handling when a typed client makes the call to the WCF service.

    Friday, December 2, 2016 12:23 PM