SvcUtil error in trace files

SvcUtil error in trace files

• psycho_billy

  /*

  please enable both system.servicemodel trace and Message trace,you can use following info(Please change initializeData path)

  it will create two e2e files,please check both e2e files for error messages

  */

   <system.diagnostics>
      <sources>
        <source name="System.ServiceModel" switchValue="Verbose, ActivityTracing"
          propagateActivity="true">
          <listeners>
            <add type="System.Diagnostics.DefaultTraceListener" name="Default">
              <filter type="" />
            </add>
            <add name="ServiceModel Listener">
              <filter type="" />
            </add>
          </listeners>
        </source>
        <source name="System.ServiceModel.MessageLogging" switchValue="Verbose, ActivityTracing">
          <listeners>
            <add type="System.Diagnostics.DefaultTraceListener" name="Default">
              <filter type="" />
            </add>
            <add name="MessageLogging Listener">
              <filter type="" />
            </add>
          </listeners>
        </source>
      </sources>
      <sharedListeners>
        <add initializeData="C:\customers\WCFMaxMessageSize\MSMQCLIENT\App_tracelog.e2e"
          type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
          name="ServiceModel Listener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
          <filter type="" />
        </add>
        <add initializeData="C:\customers\WCFMaxMessageSize\MSMQCLIENT\App_messages.e2e"
          type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
          name="MessageLogging Listener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
          <filter type="" />
        </add>
      </sharedListeners>
    </system.diagnostics>

   

   

  
  
  

• Shiloy

  SvcConfigEditor is great for enabling diagnostics. In VS | Solution Explorer, right click the config file, and select Edit WCF Configuration. In the diagnostics section, enable tracing. This will yeild an updated configuration file like Madhu shows.

  -blair

  
  

• Farzin Davari

  Thanks you beat me to it. Just found your other post.
  

• Dinus

  Madhu  is this what you mean.  If so unfortumately I don't see anything pointing to the problem in messages.e2e

  <diagnostics>

  <messageLogging

  logEntireMessage="true"

  logMalformedMessages="false"

  logMessagesAtServiceLevel="true"

  logMessagesAtTransportLevel="false"

  maxMessagesToLog="3000"

  />

  </diagnostics>

  </system.serviceModel>

  <system.diagnostics>

  <sources>

  <source name="System.ServiceModel.MessageLogging">

  <listeners>

  <add name="messages"

  type="System.Diagnostics.XmlWriterTraceListener"

  initializeData="messages.e2e" />

  </listeners>

  </source>

  </sources>

  </system.diagnostics>

   

  </configuration>

  
  

• Kevin111

  Thank you found the problem. For everyone else.- You can not have a method of the same name defined in a service contract, as one in your callbackcontract for a duplex contract.
  

• fpsoft

  Enable server side trace(verbose) and try to repro the problem,we should see some error messages in server side trace.

  -Thank you

  Madhu

  
  
  
• SvcUtil error in trace files