Compartir a través de

System.Net Tracing collection Steps

  • Artículo

Ask:
System.Net Tracing is very helpful to review SSL/TLS and socket level connection/communication failure.

To enabled tracing:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.diagnostics>
<trace autoflush="true" />
<sources>
<source name="System.Net">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.HttpListener">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.Sockets">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
<source name="System.Net.Cache">
<listeners>
<add name="System.Net"/>
</listeners>
</source>
</sources>
<sharedListeners>
<add
name="System.Net"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="c:\traces\System.Net.trace.log"
traceOutputOptions="DateTime"
/>
</sharedListeners>
<switches>
<add name="System.Net" value="Verbose" />
<add name="System.Net.Sockets" value="Verbose" />
<add name="System.Net.Cache" value="Verbose" />
<add name="System.Net.HttpListener" value="Verbose" />
</switches>
</system.diagnostics>
</configuration>

Trace Location:
Set the below path.
initializeData="c:\traces\System.Net.trace.log"

To review:
I would recommend using Notepad++.
Few pointers:
https://blogs.msdn.microsoft.com/saurabs/2012/08/16/wcf-troubleshooting-socket-abort-errors/
https://blogs.msdn.microsoft.com/saurabs/2016/03/07/wcf-review-system-net-and-network-traces-for-windows-authenticationdelegation-based-troubleshooting/
https://blogs.msdn.microsoft.com/webapps/2012/11/05/use-system-net-trace-and-ssl-alert-protocol-to-troubleshoot-ssl-connection-issue/

I hope this helps!
Saurabh Somani