thing nice that you want into the 'Source' field in
> the
> > EventLog, but if access to the registry is a problem, ...
> >
> > -BillyB
> >
> > -----Original Message-
> > From: Matthew Brown [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, Octob
at ApplicationName
> element jam something nice that you want into the 'Source' field in the
> EventLog, but if access to the registry is a problem, ...
>
> -BillyB
>
> -Original Message-
> From: Matthew Brown [mailto:[EMAIL PROTECTED]
> Sent:
yB
-Original Message-
From: Matthew Brown [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 12, 2005 5:53 AM
To: Log4NET User
Subject: Re: Inability to use EventLogAppender with ASPNET
Adding permission explicitly to the EventLog key (and all
subkeys) seems to have done the trick.
Ma
> From: "Billy Barnum" <[EMAIL PROTECTED]>
> To: "'Log4NET User'" ; "'Matthew Brown'"
> <[EMAIL PROTECTED]>
> Sent: Tuesday, October 11, 2005 5:20 PM
> Subject: RE: Inability to use EventLogAppender with ASPNET
>
>
x27;Log4NET User'" ; "'Matthew Brown'"
<[EMAIL PROTECTED]>
Sent: Tuesday, October 11, 2005 5:20 PM
Subject: RE: Inability to use EventLogAppender with ASPNET
Try removing your line:
I think what you're doing there is naming a custom EventLog with the same
nam
Try removing your line:
I think what you're doing there is naming a custom EventLog with the same
name as the existing Application log, which in turn requires write access to
the registry. Just remove that line and see what happens.
-BillyB
WILLIAM BARNUM
[EMAIL PROTECTED]
_
