The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication

by

You get this error because you let a .NET exception happen on your server side, and you didn’t catch and handle it, and didn’t convert it to a SOAP fault, either.

Now since the server side “bombed” out, the WCF runtime has “faulted” the channel – e.g. the communication link between the client and the server is unusable – after all, it looks like your server just blew up, so you cannot communicate with it any more.

So what you need to do is:

  • always catch and handle your server-side errors – do not let .NET exceptions travel from the server to the client – always wrap those into interoperable SOAP faults. Check out the WCF IErrorHandler interface and implement it on the server side

  • if you’re about to send a second message onto your channel from the client, make sure the channel is not in the faulted state:

    if(client.InnerChannel.State != System.ServiceModel.CommunicationState.Faulted)
{
   // call service - everything's fine
}
else
{
   // channel faulted - re-create your client and then try again
}

    If it is, all you can do is dispose of it and re-create the client side proxy again and then try again

More Related Contents:

  1. How i can use wcf in a wpf application [closed]
  2. What is the best workaround for the WCF client `using` block issue?
  3. WCF vs ASP.NET Web API [closed]
  4. How does WCF deserialization instantiate objects without calling a constructor?
  5. Sometimes adding a WCF Service Reference generates an empty reference.cs
  6. What are the downsides to turning off ProxyCreationEnabled for CTP5 of EF code first
  7. Pattern for calling WCF service using async/await
  8. Could not find an implementation of the query pattern
  9. Turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server
  10. Task does not contain a definition for ‘GetAwaiter’
  11. Queuing in OneWay WCF Messages using Windows Service and SQL Server
  12. Large WCF web service request failing with (400) HTTP Bad Request
  13. Simple Automapper Example
  14. WCF gives an unsecured or incorrectly secured fault error
  15. WCF Error – Could not find default endpoint element that references contract ‘UserService.UserService’
  16. Get the object is null using JSON in WCF Service
  17. Can we create custom HTTP Status codes?
  18. ASP.NET 5 add WCF service reference
  19. WCF service attribute to log method calls and exceptions
  20. Patterns for Compensating Lack of Inheritance in SOA
  21. WCF ResponseFormat For WebGet
  22. How do I prevent a WCF service from enter a faulted state?
  23. WCF: Adding Nonce to UsernameToken
  24. WCF and interfaces on data contracts
  25. How to use Custom Serialization or Deserialization in WCF to force a new instance on every property of a datacontact ?
  26. Authentication Service using WCF
  27. Efficient way to send images via WCF?
  28. Dynamically switch WCF Web Service Reference URL path through config file
  29. Error: Cannot obtain Metadata from WCF service
  30. The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8)

Leave a Comment