Write to event log c# windows server 2003

This website uses cookies We are using cookies to help make this website better. More details can be found in our Privacy Policy. Got it - do not show this message again. Privacy Policy. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website.

These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website.

These cookies do not store any personal information. You can access it through ServiceBase. The default name of the Source is the ServiceName. Show 1 more comment. Active Oldest Votes. The reason of this can be found in Event Sources Windows Dev Center I bolded the part which refers to source name : Each log in the Eventlog key contains subkeys called event sources. Improve this answer. Palec 11k 7 7 gold badges 56 56 silver badges bronze badges.

But the text you quoted says that you have to register the event source under the Event log key. What I meant is that the Event Log's name is often the same name of the application, so that is why you can register an eventlog entry directly to the EventLog without creating a new source. I bolded the quouted text for further readings. Technically the act of creating the registry key is registering the event source. Naming the key after the application name is a convention to avoid conflicts.

Your answer is basically the same as this answer. Thanks for your time Raymond Chen, we are here to try to solve or suggest something that might help others. In this case I believe I answered the topic question: "Is there a way to write to this event log: Or at least, some other Windows default log, where I don't have to register an event source? Despite of the fact that it might cause conflicts as you said, it exists a way. You are answering the question "Is there a way to do it without registering an event source?

Show 3 more comments. In my test under Windows Server r2, I however get the following log entry using "Application" source: The description for Event ID xxxx from source Application cannot be found. SourceExists eventSource ; if! It is also possible to create the source externally, e. Add a comment. CodeCaster CodeCaster k 19 19 gold badges silver badges bronze badges. Then use an installer stackoverflow. Thank you. This lead me to this other SO question: stackoverflow.

CodeCaster - From where we can access these logs? Derek Schauland has been tinkering with Windows systems since Miss a Windows Server tip? Editor's Picks. The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script. TasksBoard is the kanban interface for Google Tasks you've been waiting for.

Paging Zefram Cochrane: Humans have figured out how to make a warp bubble. EventLog Access using impersonation in Windows Server Can't read the appSettings section of web. NET Framework. C Application not allowed to write to event log on Windows Server NET 2.

Windows Server problems. Mobile Development. Ms access. Undesired Name? Append Query trying not to add duplicate records to new table. Follow us! Get the Latest Bytes Updates.