If you want to setup SvcTraceViewer properly, it's easily done in 6 steps...

1. Download the Windows SDK so that you can get your hands on the the SvcTraceViewer that you will then find in

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin

2. Make your life simpler by adding the above path the PATH environment so that every time you have to go back to command line you don't pull your hair out:

3. Add listeners to your client (or server) config file... put pay attention here...there are TWO listeners you have to hook up.
One of the listeners is for general message activity -- the other contains the message proper -- and that's really useful when dealing with SOAP.

<system.diagnostics>
  <sources>
    <!-- Logging of actual WCF Activity -->
    <source name="System.ServiceModel" 
            propagateActivity="true" 
            switchValue="Information,ActivityTracing">
      <listeners>
        <add name="wcfListener"/>
      </listeners>
    </source>
    <!-- Logging of actual WCF Message -->
    <source name="System.ServiceModel.MessageLogging">
      <listeners>
        <add name="wcfListener"/>
      </listeners>
    </source>
  </sources>
  
  <sharedListeners>
    <!-- A single listener for both streams of logging...-->
    <add name="wcfListener" 
         type="System.Diagnostics.XmlWriterTraceListener" 
         initializeData="..\..\wcf.svclog"/>
  </sharedListeners>

  <!-- Slows things down, but we are debugging anyway, 
       so don't worry about it right now... -->
  <trace autoflush="true" />
  
</system.diagnostics>

Note how:

• the initializeData is using backward slashes as we're talking about a file system path (it fails if forward slashes btw) and
• we've requested to back it up out of the Client/Bin/Debug/ to the solutions  root directory -- I find that easier when debugging but you do what you want...

4. You're not done yet...we have to go back to express what has to be logged of the message:

<system.serviceModel>
...
  <diagnostics>
    <messageLogging
      logEntireMessage="true"
      logMessagesAtServiceLevel="true"
      logMalformedMessages ="true"
      logMessagesAtTransportLevel="true">
    </messageLogging>
  ...
</diagnostics>

system.serviceModel>

6. I then make my life a little easier by writing a *.bat file in the solution root that contains:

SVCTraceViewer "wcf.svclog"

Now all you have to do is right click the solution to Open Folder in Windows Explorer to see:

in order to click the *.bat file to pull up the svctraceViewer: