Nagevlog tries to do this.
It gets the message source, ID, severity and any parameters from the eventlog.
It attempts to get the message display format from the relevant DLL and render the message in this format; if it cannot, it simply appends the parameters.
It creates a message header with the severity, source and number in a standard format.
In this case, it looks like for some reason it was unable to obtian the display format "%s service started" from Windows and so just used the parameter.
THis may be because you have a more recent version of windows that forces double-byte chars? Nagevlog has problems with wide characters
Login
Register
FAQ
Members
