Events generated in the application log with severity codes 8 and 16 do not match. (NETIQKB29966)

fact
VigilEnt Security Agent for Windows 3.x

fact
VigilEnt Security Agent for Windows Detect 

symptom
Events generated in the application log with severity codes 8 and 16 do not match.

cause
VigilEnt Security Agent for Windows Detect event in the Application Event log shows the correct severity number at the beginning of the Description within the event. The severity that is displayed  further into the Description is Microsoft's severity number.

fix

Please refer to the  list of Microsoft's severity information below:

VALUE                                                                              MEANING

EVENTLOG_ERROR_TYPE                                                Error event 
EVENTLOG_WARNING_TYPE                                           Warning event 
EVENTLOG_INFORMATION_TYPE                                    Information event 
EVENTLOG_AUDIT_SUCCESS                                          Success Audit event        
EVENTLOG_AUDIT_FAILURE                                           Failure Audit event 

#define EVENTLOG_SUCCESS                                         0x0000

#define EVENTLOG_ERROR_TYPE                                  0x0001

#define EVENTLOG_WARNING_TYPE                             0x0002

#define EVENTLOG_INFORMATION_TYPE                     0x0004

#define EVENTLOG_AUDIT_SUCCESS                           0x0008

#define EVENTLOG_AUDIT_FAILURE                            0x0010 = the hex and its decimal value is 16.

Formerly known as NETIQKB29966