Windows Event log issues

SGAITS

We are using management software to monitor event logs for errors.  We forced a backup failure to gather information about the event log entry that the Backupper produces.  Unfortunately, there was an issue with the event ID, in that there was no information passed.  Please take a look and address this issue.

Here is the Event log in question:

-------------------------------------------------------------

Log Name:      Application

Source:        Backupper Service

Date:          12/30/2014 7:00:57 PM

Event ID:      0

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      TEST-PC1

Description:

The description for Event ID 0 from source Backupper Service 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.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Backupper Service

Create Process Successful.

Commond line: C:\Program Files (x86)\AOMEI Backupper Standard Edition 2.2\Backupper.exe d3b75cf6-3f1d-4c04-aa15-92fd951695da 1

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt;

  <System>

    <Provider Name="Backupper Service" />

    <EventID Qualifiers="0">0</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-12-31T00:00:57.000000000Z" />

    <EventRecordID>20390</EventRecordID>

    <Channel>Application</Channel>

    <Computer>TEST-PC1</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Backupper Service</Data>

    <Data>Create Process Successful.

Commond line: C:\Program Files (x86)\AOMEI Backupper Standard Edition 2.2\Backupper.exe d3b75cf6-3f1d-4c04-aa15-92fd951695da 1</Data>

  </EventData>

</Event>

-------------------------------------------------------------

Thank you!

YoungCheng

Hi，

Sorry for the late,I sent the issue you pointed out to our development team, and it was an issue we pay little attention in the past. We will improve it in the future. 

SGAITS

Thank you!

darylsonnier

SGAITS,

Just as a bit of background information, writing errors to the event log in Windows is a multiple step process.  First you have to engage the event service.  Next you have to create an event with a given ID.  In order for that ID to show any information, the program must register itself with the event service and provide text along with an accompanying ID.  If this part isn't done, you can still write to the event log, but there won't be any useful information other than that some unknown event occurred.  This is why your log entry from above said there was no data.  The software had never written a description into the registered list of events, so the event viewer had nothing to pull from to interpret the error code.