The problem with the event logs is they are notoriously uninformative. It seems that their purpose is to taunt IT personnel, by suggesting some helpful information is available. Yeah, right. There are entire Web sites dedicated to deciphering event identification numbers mean. The necessity for such sites is just plain sad. Apparently, leaving what happened a mystery is a better alternative to including actual WORDS that describe the problem, in human language.
I implore you: do not be that kind of developer! I always insist on making everything human readable, and easy to understand. By leveraging the extensible nature of .NET, we can easily log useful and meaningful information to the event log, which will help the user or IT administrator fix the problem, and/or help the developer debug the issue.
Here's how you can use a single method, to alleviate the IT admin's urge to strangle you.