Yeah, it looks like that the calls to RegisterEventSource in the nteventlog.cpp program might be out of sync.
In the Java_org_apache_log4j_nt_NTEventLogAppender_registerEventSource function (for initial event source registration): jint handle = (jint)RegisterEventSource(nserver, nsource); In the Java_org_apache_log4j_nt_NTEventLogAppender_reportEvent function (for subsequent event reports): handle = (jint)RegisterEventSource(NULL, "Log4j"); It looks like the RegisterEventSource call during the initial event source registration (Java_org_apache_log4j_nt_NTEventLogAppender_registerEventSource) may not have the proper source available, which causes the Log4j source missing from the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\So urces as seen in my event log test from eventcreate command for the registry inspection. Regards, Shuh -----Original Message----- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 10:10 AM To: Log4J Users List Subject: Re: NTEventLogAppender with missing description source for Windows Server 2003 Sorry, I'm on the road at the moment and don't have access to my Windows development resources. As far as I can tell from your description the appender is working as expected. It does log the message to the EventLog, it just has never implemented the code to register a corresponding message description. regsvr32 does not find the entry point since there is no RegisterDll entry point since the DLL does not register any resources (likely it should). 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. --------------------------------------------------------------------- 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]
