Hi Emilie, Thanks for your inquiry. Please keep all inquiries on the log4j-user list.
No, I have not heard much back to resolve this issue. I am hoping that someone who knows the answer could help out. Basically, the NTEventLogAppender works to capture the log information in the Event Viewer, except that it also generates those extra annoying messages for every log that you send. These extra messages clog up (and probably mislead) the real log message that makes the NTEventLogAppender somewhat unrealistic for a real application. The real issue is that NTEventLogAppender itself does not register properly with regsvr32 to begin with. Curt Arnold earlier gave some clues on that as he wrote: "If it appears to be missing header files, it is likely files that are produced by javah that generate the header required to implement the java native methods." Since the downloaded log4j package does not provide complete source files required to build the whole DLL thing, I was hoping that someone involved in the log4j development could provide some more help here. Regards, Shuh ------------------------------------------------------------------------ -------- From: PERTUISET Emilie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 13, 2006 4:08 AM To: CHANG Shuh Subject: Problem Event Id 4096 and log4j Hello, I have seen on a web site that you had had the following problem : However, for the NTEventLogAppender appender, I keep getting annoyingEventLog message in the Event Viewer:The description for Event ID ( 4096 ) in Source ( Log4j ) cannot be found.The local computer may not have the necessary registry information ormessage DLL files to display messages from a remote computer. You may beable to use the /AUXSOURCE= flag to retrieve this description; see Help andSupport for details. The following information is part of the event: [myreal log info displays correctly here...]I have searched for an answer for this (well-known?) problem. However, allthe "solutions" that I found so far do not apply to my situation. Have you had an answer for this problem? Or did you find a solution? I will be very interested by this one. I have the same problem and I use log4j-1.2.14. Thank you, in advance, for your help. Best Regards, Emilie Pertuiset -----Original Message----- From: Shuh Chang [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 1:58 PM To: Log4J Users List Subject: RE: NTEventLogAppender with missing description source for Windows Server 2003 I need to make a correction: I just found out that the NTEventLogAppender.dll *does* create the default "Log4j" entry (or any other source specified in the log4j.properties) in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Applicatio n\So urces registry. That's my mistake. Sorry about that. Nonetheless, the NTEventLogAppender.dll still couldn't be properly loaded/registered in the registry by the regsvr32 command, which causes the extra annoying messages in the event viewer. Regards, Shuh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
