Databases
StackOverflow2013
Postsdbo
POCan't get Log4Net to work in our WCF application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't get Log4Net to work in our WCF application
    primarykey
    data
    text
    <p>We are trying to use Log4Net to log from our IIS 6-deployed WCF Application. We are trying to log to a file, but can't seem to get the log files to be created, let alone see the logging output in them. The pertinent pieces of out web.config are:</p> <pre><code>&lt;sectionGroup name="common"&gt; &lt;section name="logging" type="Common.Logging.ConfigurationSectionHandler, Common.Logging" /&gt; &lt;/sectionGroup&gt; ... &lt;common&gt; &lt;logging&gt; &lt;factoryAdapter type="Common.Logging.Simple.TraceLoggerFactoryAdapter, Common.Logging"&gt; &lt;arg key="level" value="INFO" /&gt; &lt;arg key="showLogName" value="true" /&gt; &lt;arg key="showDataTime" value="true" /&gt; &lt;arg key="dateTimeFormat" value="yyyy/MM/dd HH:mm:ss:fff" /&gt; &lt;/factoryAdapter&gt; &lt;/logging&gt; &lt;/common&gt; &lt;log4net&gt; &lt;appender name="FileAppender" type="log4net.Appender.RollingFileAppender"&gt; &lt;param name="File" value="c:\logs\ApplicationInfoTest.log" /&gt; &lt;threshold value="INFO" /&gt; &lt;param name="AppendToFile" value="true" /&gt; &lt;param name="DatePattern" value="ddMMyyyy" /&gt; &lt;param name="MaxSizeRollBackups" value="10" /&gt; &lt;param name="MaximumFileSize" value="10MB" /&gt; &lt;param name="RollingStyle" value="Size" /&gt; &lt;param name="StaticLogFileName" value="true" /&gt; &lt;layout type="log4net.Layout.PatternLayout"&gt; &lt;param name="Header" value="\r\n\r\n---------------------------------------------\r\n" /&gt; &lt;param name="Footer" value="\r\n---------------------------------------------\r\n\r\n" /&gt; &lt;param name="ConversionPattern" value="%d [%t] %-5p - %m%n" /&gt; &lt;/layout&gt; &lt;/appender&gt; &lt;root&gt; &lt;level value="INFO" /&gt; &lt;appender-ref ref="FileAppender" /&gt; &lt;/root&gt; &lt;/log4net&gt; </code></pre> <p>With this configuration we can see INFO level logging coming out of our application when using DebugView, but it is clear that this is from the piece and not the<br> piece. </p> <p>Is there something that we have failed to set up in web.config? Is it a permissions issue with the directory we have created for the logs to be written to?</p> <p>Please point out our obvious mistake.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAndrew Harmel-Law
    plurals
    1. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCan't get Log4Net to work in our WCF application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCan't get Log4Net to work in our WCF application
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCan't get Log4Net to work in our WCF application
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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