Ok ended up being a bunch of issues, the main one being that for some
reason the configuration call was not being picked up in my global.asax
file.
protected void Application_Start( object
sender, EventArgs e )
{
log4net.Config.XmlConfigurator.Configure();
I read somewhere that if you change the 'Managed Pipeline Mode' of the
application pool from Integrated to Classic (IIS 6) that this would fix
things however it didn't seem to help in my case. So now pulled the
configuration call out into a http module to ensure its all setup.
Once I got that going I just used the log4net internal log and a trace
listener to work out what else was wrong with things.
So yeah, thanks everyone for your help. A pretty silly fix in the end.
From: [email protected]
[mailto:[email protected]] On Behalf Of Michael Minutillo
Sent: Thursday, 1 July 2010 10:41 AM
To: ozDotNet
Subject: Re: log4Net on Windows server 2008
Hi David,
What sort of issues are you having? Windows 2008 is probably:
a) Packed full of more fine grained security controls AND
b) Even more secure by default
Failing that here are a few questions that you've probably already gone
through yourself:
* Are the framework versions the same?
* Are the App Pools configured the same?
* Can you get a simple one page app with log4net working? i.e. Is it
log4net or the config
* Can you get log4net working in a console app on that machine? i.e. Is
it IIS/ASP.NET
On Thu, Jul 1, 2010 at 10:32 AM, David Walker
<[email protected]> wrote:
Hey guys,
Has anyone had any issues with getting log4net working in an ASP.Net
project running on Windows Server 2008 (IIS 7). My configuration works
on both my Windows 7 development machine and another windows server 2003
web server. I have cut the config down but still nothing works.
This is a pretty broad question but I am kind of out of ideas.
Cheers,
Dave
--
Michael M. Minutillo
Indiscriminate Information Sponge
Blog: http://wolfbyte-net.blogspot.com
