>Hi All,
>
>I am having a difficult time resolving a WCF service error exception of "ServiceChannel, cannot be used for communication because it is in a Faulted state". I have googled this error with lots of hits and for one learned the service does not return the details of the actual error.
>
>This leads me to believe it must be with the WCF service and not my client application that uses it. At this point all I seem to be able to do is experiment trying to find something which has an affect. If anyone has any ideas, I would really love to hear them.
>
>PS: I posted a similar question earlier but never have seen it show up so if it gets posted twice, I appologize.
>Tim

What protocol? Is it establishing a connection then failing, or (I'm assuming) it's failing with that error as soon as you try to open the connection?

You can enable all the debugging and use their tracing tool to help debug this. In Visual Studio select Tools > WCF Service Configuration Editor and open the server .config file, then go to Diagnostics and click on the link to enable tracing and the link to enable message logging. Save it and do the same with the client (going from memory here, hopefully this at least gets you in the ballpark).

Once tracing is enabled fire up the server and attempt to connect. If you don't already have it, you'll also want the Service Trace Viewer Tool which is included with the Windows SDK (\Program Files\Microsoft SDKs\Windows\v6.0A\bin\SvcTraceViewer.exe). You can fire it up and load the log files. It's actually pretty easy to poke around from there (although there is a ton of information displayed, hopefully you've got a nice high resolution monitor). If you don't have the SDK (or don't want to install it because it's huge), let me know - I can e-mail the file to you if you want.