Common.Logging is not working any more

[Suter]

Without changing the source code suddenly Common.Logging in quartz.net
is not working any more on the remote server side. Version conflict?
Any idea?
Is there anywhere good documentation about Common.Logging?

Cheers Pascal

[Marko Lahma]

Hi,

Common.Logging home page is located here: http://netcommon.sourceforge.net/

Usually you would refer to true implementation documentation, like
log4net though. The logging shouldn't magically stop if you haven't
made any configuration changes...

-Marko

> --
>
> You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
> To post to this group, send email to quar...@googlegroups.com.
> To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.
>
>
>

[phil]

Hi Pascal,

This could of course be due to many different things, but I hit one
today that took me a while to work out which I thought I'd share.

I had the out-of-the-box Quartz.Net Windows Service running and
logging fine to the Application EventLog, and a Windows Form test bed
application with exactly the same configuration (both quartz and
log4net). My Windows Forms TestBed was not logging.

This is due to a security exception that is caught and swallowed by
log4net. Remember in Vista and above, access to the EventLog is not
allowed by default, so either run the application as Administrator,
disable UAC or use a System account if you wish to use the EventLog.

Cheers,
Phil.
PS Happy New Year!