Communication object in the faulted state RRS feed

  • General discussion

  • I'm going through the pain of deploying my WCF services to an SSL production environment.  Whenever I call a service from the code, I get this exception:

     Message: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.,

    My thinking was that if I turned on diagnostics for messaging and activation, I would hopefully get some very useful information on what the real underlying problem.

    As it stands, my messaging logging works, but there's no additional info provided beyond the error above.  The activation log hasn't been created in my log directory and I've verified the switches, path location, etc.

    So, this raises the question:  What are some ways I can get to the real problem? 


    • Changed type Marco Zhou Monday, March 9, 2009 8:13 AM OP doesn't revert back
    Tuesday, February 24, 2009 7:55 PM

All replies

  • You are invoking service operation on an already faulted channel, are you able to call the service operation by instantiating a new client proxy(ClientBase or ChannelFactory)?


    Another Paradigm Shift
    Friday, February 27, 2009 10:26 AM
  • We are changing the issue type to “Comment” because you have not followed up with the necessary information. If you have more time to look at the issue and provide more information, please feel free to change the issue type back to “Question” by clicking the "Options" link at the top of your post, and selecting "Change Type" menu item from the pop menu. If the issue is resolved, we will appreciate it if you can share the solution so that the answer can be found and used by other community members having similar questions.


    Thank you!

    Another Paradigm Shift
    Monday, March 9, 2009 8:13 AM