title: Is it acceptable to write to the Application Event Source?
body: <p>There are certain circumstances in our application where non-fatal errors occur and the application recovers.  </p>
  
  <p>An example of this failing to correctly identify some importable items when populating said items to a selection list.  The errors won't crash the app but a user would be alerted that some of the items failed to load.</p>
  
  <p>In this case, the error is logged to the Application event log as a warning.  It's a non-fatal error that the app recovers from, but logging to the event log allows us to see the original error if need be.</p>
  
  <p>Our problem is that the software needs to be able to be installed with a Power User account. Not being an admin account, we won't have the ability to create custom event sources for the application.</p>
  
  <p>The aim is to write the errors instead to the "Application" event source (which already exists appears in the Application event log).  Doing this, however, causes text similar to the following to also be included.</p>
  
  <p><i>The description for Event ID 0 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.</i></p>
  
  <p>This is because the EventID is 0 when we write it. This approach will get the job done, but is there a a better way?  Is there a non-admin way to specify the EventID for the Application Event source to indicate that it came from our app?</p>