This sounds to me like a security issue. See the FAQ entry "Why doesn't the EventLogAppender work?" as well as this excerpt from a recent post of mine.
- The FAQ entry, "Why doesn't the EventLogAppender work?" talks to this issue a bit, and mentions 2 methods for allowing your app to have write authority and have its own 'Source' field. But there is a 3rd, registry-hack method for those of you who didn't know (And I didn't until just now) and don't want to create an EventLogInstaller, but just write to the Application Log. See http://support.microsoft.com/default.aspx?scid=kb;en-us;329291 , and add <applicationName value="myEventSource" /> to your EventLogAppender description in your config file. One thing the article doesn't mention, though: after you create the key, you have to add a string value to it with the name ' EventMessageFile' and an actual value of ' C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\EventLogMessages.dll', or current version of that assembly. Look at some of the other keys in the vicinity for examples. WILLIAM BARNUM 14076 Rosario Rd. Anacortes, WA 98221-8559 Phone: 360.299.3830 Cell: 360.202.3670 [EMAIL PROTECTED] -----Original Message----- From: Ganapatiraju, Shiva (OCFS) [mailto:[EMAIL PROTECTED] Sent: Friday, September 23, 2005 2:25 PM To: Log4NET User Subject: RE: How to log EventID with EventLogAppender? Even after log4net.ThreadContext.Properties("EventId") = 5 log4net.ThreadContext.Stacks("EventId").Push("5") log.Error("Error Login Page.", ex) I am getting this error. The description for Event ID ( 0 ) in Source ( SSOPWebError ) 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: Any suggestions are greatly appreciated Shiva Ganapatiraju New York State Office of Children & Family Services Information Technology/SSOP Project 518.403.9056 [EMAIL PROTECTED] http://ocfs.state.nyenet/admin/ofm/rsu
