The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
For me it was a load balancer/url issue. A web service behind a load balancer called another service behind the same load balancer using the full url like: loadbalancer.mycompany.com
. I changed it to bypass the load balancer when calling the second service by using localhost.mycompany.com
instead.
I think there was some kind of circular reference issue going on with the load balancer.