Event Log Weirdness.

Hi All, I'm just looking into an odd issue. I have an EventLogAppender being configured in C#. If I set this up to append to the Application log all is fine. However, when I ask it to create a custom event log called LogTest its not working as expected. Now the obvious thing is that the

RE: Event Log Weirdness.

I should also point out that I know the Threshold is Off ... I have explicit methods that switch this on in order to prevent the event log from being swamped with log entries as the processes we run here could produce millions of logs a day ... Our default log destination is a SQL Database ...

RE: Event Log Weirdness.

Do you call ActivateOptions() when Threshold property is changed? Radovan -Původní zpráva- Od: James Green [mailto:james.gr...@occam-dm.com] Odesláno: 19. června 2009 12:00 Komu: Log4NET User Předmět: RE: Event Log Weirdness. I should also point out that I know the Threshold is Off ...

RE: Event Log Weirdness.

Do you call ActivateOptions() when Threshold property is changed? Radovan Indeed I do ... public static void LogToEventLog(bool logToEventLog) { if (_eventLogAppender == null) return; if (logToEventLog) {

RE: Event Log Weirdness.

Hi Again, I seem to have some info to work on. Trying to log into my custom event log has generated this in the Application event log: The description for Event ID ( 0 ) in Source ( MyFirstApp ) cannot be found. The local computer may not have the necessary registry information or message DLL

EventLog Fun Continued.

Hi All, I'm still at a total loss as to how to get log4net successfully writing to a custom event log, writing to the Application event log is working exactly as expected. I have started using the IEventIDLog extension in order to pass over event IDs to the log messages to see if this makes

unsubscribe

RE: Mystery concerning configuration SOLVED.

I have discovered the source of the problem. We had split out the log4net configuration from the web.config but with a redirection left inside the web.config of the form: log4net file=other_config_directory/log4net.config / The file at the end was of the correct syntax and could be used

Getting AdoNetAppender parameters using Log4Net API

Hello, I've defined some extra parameters for AdoNetAppender in log4net config file. Everything works fine. Here is one of my extra parameters defined: parameter parameterName value=@cachetid/ dbType value=String/ size value=36/ layout

Re: unsubscribe

I think you need to send an email to a special unsubscribe address, not just a subject with unsubscribe as the subject. - Original Message From: Laurence Hunter cazador7...@yahoo.com To: Log4NET User log4net-user@logging.apache.org Sent: Friday, June 19, 2009 12:51:17 PM Subject:

Re: Getting AdoNetAppender parameters using Log4Net API

Surprisingly the parameters collection isn't exposed publicly so you'd have to extend the built-in AdoNetAppender and expose them: public class AdoNetAppender2 : AdoNetAppender { public AdoNetAppenderParameter[] GetParameters() { return

RE: Mystery concerning configuration SOLVED.

Actually, the file attribute on the log4net node is processed by the .NET framework as a redirection to the given file. The attribute tells .NET to look for the actual definition of the section in the given file. log4net should be oblivious to this but it is not. The behavior seen is that