logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Taylor" <cstay...@java-internals.com>
Subject Re: NTEventLogAppender - remove ugly description message?
Date Fri, 10 Aug 2001 00:25:43 GMT
Sorry about the repeat emails....

Yeah, the problem is that the Event Viewer application needs to load the
resource dll, so I'm pretty sure that if you don't supply a complete path to
the DLL in the registry entry, it defaults to looking in the WINNT and
WINNT\system32 directory.

Glad you got it working,
-Chris
----- Original Message -----
From: "Jerome Jacobsen" <jerome.jacobsen@gentootech.com>
To: "LOG4J Users Mailing List" <log4j-user@jakarta.apache.org>
Sent: Friday, August 10, 2001 1:56 AM
Subject: RE: NTEventLogAppender - remove ugly description message?


> I placed NTEventLogAppender.dll in the C:\WINNT\system32 directory.  It is
> now working correclty.  The DLL was in my PATH before
(C:\jdk1.3.1\jre\bin).
> Not sure why that didn't work completely.
>
> -Jerome
>
> -----Original Message-----
> From: Christopher Taylor [mailto:cstaylor@java-internals.com]
> Sent: Thursday, August 09, 2001 12:27 PM
> To: LOG4J Users Mailing List; jerome.jacobsen@gentootech.com
> Subject: Re: NTEventLogAppender - remove ugly description message?
>
>
> No problems... yeah, it's the NTEventLogAppender.dll.  According to the
make
> file, the resources are included in the DLL.
>
> AddRegistryInfo is a function (sorry about the misnomer) in the
> nteventlog.cpp file.  It's responsible for adding the appropriate registry
> entry for the message dll (the NTEventLogAppender.dll).  It only needs to
> run once, and you can verify if it has been run by opening the registry
> editor and checking the values of the key
>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\[s
> ource name], where source name is the string passed into the
> NTEventLogAppender method registerEventSource.  If you look at the source
> code for NTEventLogAppender.java, you'll see that the default source name
is
> Log4J.
>
> If the NT Event Viewer is giving you grief, the reason is that the
> NTEventLogAppender.dll hasn't been registered properly in the NT registry,
> or that the Event Viewer application can't find the DLL.  If you check the
> registry as above and send me the results, I'll see what I can do.
>
> -Chris
> ----- Original Message -----
> From: "Jerome Jacobsen" <jerome.jacobsen@gentootech.com>
> To: "LOG4J Users Mailing List" <log4j-user@jakarta.apache.org>
> Sent: Thursday, August 09, 2001 11:23 PM
> Subject: RE: NTEventLogAppender - remove ugly description message?
>
>
> > Please excuse my NT ignorance.  When you say the 'message resource DLL'
> are
> > you referring to the NTEventLogAppender.dll or some other DLL?
> > NTEventLogAppender.dll is in my path.  If it wasn't I would get an
> exception
> > (java.lang.UnsatisfiedLinkError).
> >
> > What is addRegistryInfo?  It doesn't appear to be a method on
> > NTEventLogAppender class, at least not the version in Log4j 1.1.3.
> >
> > -Jerome
> >
> > -----Original Message-----
> > From: Christopher Taylor [mailto:cstaylor@java-internals.com]
> > Sent: Thursday, August 09, 2001 10:04 AM
> > To: LOG4J Users Mailing List; jerome.jacobsen@gentootech.com
> > Subject: Re: NTEventLogAppender - remove ugly description message?
> >
> >
> > Yes, the message resource DLL needs to be registered in the NT Registry.
> > The code addRegistryInfo handles that for you, so you need to make sure
> that
> > the NTEventLogAppender.dll is in your PATH (the windows system directory
> > should work AFAIK).
> >
> > -Chris
> > ----- Original Message -----
> > From: "Jerome Jacobsen" <jerome.jacobsen@gentootech.com>
> > To: <log4j-user@jakarta.apache.org>
> > Sent: Thursday, August 09, 2001 10:43 PM
> > Subject: NTEventLogAppender - remove ugly description message?
> >
> >
> > > I just tried out the NTEventLogAppender.  When I view the event in the
> > Event
> > > Viewer the Description says the following.
> > >
> > > 'The description for Event ID ( 4096 ) in Source ( Log4jTester )
cannot
> be
> > > found. The local computer may not have the necessary registry
> information
> > or
> > > message DLL files to display messages from a remote computer. The
> > following
> > > information is part of the event: Exiting application.'
> > >
> > > I was expecting just 'Exiting application.'
> > >
> > > Does anyone know how to get rid of that extra stuff that's getting
added
> > to
> > > my message?
> > >
> > > Regards,
> > >
> > > Jerome
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: log4j-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-user-help@jakarta.apache.org
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message