Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A few places to start looking are:</p> <ol> <li><p>Did you use EntLibConfig.exe to build the web.config? This is an exe that comes with Enterprise Library, you should find it in the Bin directory of the Enterprise Library install in Program Files - it gives you a reasonably intuitive graphical interface to set up enterprise library for an application: just point it at the config file for your application and set up the things you want.</p></li> <li><p>For database logging you need to configure your connection strings using the Data Access Application Block - you will need another section in your config file for this.</p></li> <li><p>For your database connection string, what authenticaion mode are you using? Does the user identity running the application have write access to the logging database?</p></li> <li><p>Do you have other database connectivity?</p></li> </ol> <p>Also - if you are running the .Net framework 3.5 you should consider using version 4.1 of the Enterprise Library.</p> <p><strong>EDIT after config file supplied</strong></p> <p>Looking at the config file you've attached (you may want to remove the passwords by the way) I think that you are missing a logging exception handler - the only exception handler you appear to have is a wrap exception handler.</p> <p>Below is an example of one of one of my exception handling policies (from 4.1 of the Enterprise Library but yours should be similar).</p> <pre><code>&lt;exceptionPolicies&gt; &lt;add name="Data Layer Policy"&gt; &lt;exceptionTypes&gt; &lt;add type="System.Exception, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" postHandlingAction="NotifyRethrow" name="Exception"&gt; &lt;exceptionHandlers&gt; &lt;add logCategory="DataLayer" eventId="100" severity="Error" title="Data Layer Exception" formatterType="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.TextExceptionFormatter, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="0" useDefaultLogger="false" type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.LoggingExceptionHandler, Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" name="Logging Handler" /&gt; &lt;/exceptionHandlers&gt; &lt;/add&gt; &lt;/exceptionTypes&gt; &lt;/add&gt; &lt;/exceptionPolicies&gt; </code></pre> <p>The wrap handler is used where you want to wrap one exception around another. You can have both a logging handler and a wrap handler if that is needed - the logging handlers fire before the wrapping ones.</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