This could happen if you run LogParser on the computer where you don't have a valid source for the remote event in a registry.
You may:
1. Run LogParser on the pc where you have your log file to analyze.
2. Add a source to the local registry of the computer with the LogParser.
Here's how I did it for IBM ServeRAID manager:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\ServeRAID Manager Agent]
"EventMessageFile"="c:\\program files\\ibm\\serveraid manager\\ntlogmsg.dll"
By that, you're telling your local eventlog subsystem to use ntlogmsg.dll file as a source with event descriptions.
Hope that helps