title: Trace a .NET 1.1 Web Service call
body: <p>I'm having an issue trying to find an error with a web service using .NET 1.1. In .NET 2.0/3 I can add a trace section to my web config like:</p>
  
  <pre><code>&lt;system.diagnostics&gt;
      &lt;trace autoflush="true" /&gt;
      &lt;sources&gt;
        &lt;source name="System.Web.Services.Asmx"&gt;
          &lt;listeners&gt;
            &lt;add name="AsmxTraceFile" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\subconnector\local.log" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId" /&gt;
          &lt;/listeners&gt;
        &lt;/source&gt;
      &lt;/sources&gt;
      &lt;switches&gt;
        &lt;add name="System.Web.Services.Asmx" value="Verbose"  /&gt;
      &lt;/switches&gt;
    &lt;/system.diagnostics&gt;
  </code></pre>
  
  <p>And that works great, I get detailed logs of what is hitting the service. But when I tried to use that in a .NET 1.1 site, it gave an error - it does not recognize the  tags. So using what I could find while googling, I trimmed it down to:</p>
  
  <pre><code>&lt;system.diagnostics&gt;
      &lt;switches&gt;
        &lt;add name="General" value="4" /&gt;
        &lt;add name="Data" value="1" /&gt;
        &lt;add name="System.Web.Services.Asmx" value="4" /&gt;
      &lt;/switches&gt;
      &lt;trace autoflush="true" indentsize="4" &gt;
          &lt;listeners&gt;
            &lt;add name="TextListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="d:\logfiles\local.log"  /&gt;
          &lt;/listeners&gt;
      &lt;/trace&gt;
  &lt;/system.diagnostics&gt;
  </code></pre>
  
  <p>(I added the "General" and "Data" lines .. because I saw that in the MSDN page for the switches...)</p>
  
  <p>But nothing is written to my log file. The file gets created, but no output. Anyone have any insight on how to get tracing?</p>
  
  <p>(My problem is, a consumer of our web service is getting a "network error" - We can see a IIS log entry when they try to access the service, but there's no other indication it gets past the initial IIS hit - no other logs are written. We can hit the web service using the discovery page (hitting the .asmx page), and it works fine.)</p>
  
  <p>Thanks.</p>