Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In my experience, log4net usually swallows any internal errors, simply resulting in log statements that do not produce any results.</p> <p>What you may want to try is enable log4net's internal logging. You can do this by adding the following to your <code>appSettings</code> section:</p> <pre><code>&lt;add key="log4net.Internal.Debug" value="true" /&gt; </code></pre> <p>This sets the property <a href="http://logging.apache.org/log4net/release/sdk/log4net.Util.LogLog.InternalDebugging.html" rel="noreferrer"><code>LogLog.InternalDebugging</code></a> to <code>true</code>. log4net will now log to the standard output and error streams and to configured trace listeners.</p> <p>You can use the <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.textwritertracelistener.aspx" rel="noreferrer">following configuration</a> to capture any messages logged to tracing:</p> <pre><code>&lt;system.diagnostics&gt; &lt;trace autoflush="false" indentsize="4"&gt; &lt;listeners&gt; &lt;add name="myListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\TextWriterOutput.log" /&gt; &lt;remove name="Default" /&gt; &lt;/listeners&gt; &lt;/trace&gt; &lt;/system.diagnostics&gt; </code></pre> <p>All messages logged by log4net internally will appear in <code>TextWriterOutput.log</code>. If you get a <code>SecurityException</code> when you add the trace listener to your configuration, then very probably the apppool identity does not have sufficient rights to create a file at the specified location (in the example: <code>c:\</code>). Try another location or give the apppool identity sufficient rights.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload