I have a small app which tries reading the system, application, and security
event logs within Vista. Many of the event logs return with a generic
sentance indicating that:
"The description for Event ID '1073742825' in Source 'LoadPerf' cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display the message, or you may not have permission to
access them."
The Event ID and Source differ from log to log but in all cases the
reported Event ID in the message does not match the actual Event ID shown by
Vista. Many times the Event ID within the message is a negative number.
I don't have control over the "number" within the message. I believe the
reason for this message appearing is because the "bad" Event ID in the
message doesn't correspond to any valid Event ID that Vista understands. Has
anyone seen this before?
Here is a code snippet that shows the problem.
EventLogPermiss ion elPermission = new
EventLogPermiss ion(PermissionS tate.Unrestrict ed);
System.Diagnost ics.EventLog eLog = new EventLog("Syste m", ".");
EventLogEntryCo llection logs = eLog.Entries;
foreach (EventLogEntry entry in logs)
{
Debug.WriteLine (entry.Message) ;
}
--
-----------
Thanks,
Steve
event logs within Vista. Many of the event logs return with a generic
sentance indicating that:
"The description for Event ID '1073742825' in Source 'LoadPerf' cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display the message, or you may not have permission to
access them."
The Event ID and Source differ from log to log but in all cases the
reported Event ID in the message does not match the actual Event ID shown by
Vista. Many times the Event ID within the message is a negative number.
I don't have control over the "number" within the message. I believe the
reason for this message appearing is because the "bad" Event ID in the
message doesn't correspond to any valid Event ID that Vista understands. Has
anyone seen this before?
Here is a code snippet that shows the problem.
EventLogPermiss ion elPermission = new
EventLogPermiss ion(PermissionS tate.Unrestrict ed);
System.Diagnost ics.EventLog eLog = new EventLog("Syste m", ".");
EventLogEntryCo llection logs = eLog.Entries;
foreach (EventLogEntry entry in logs)
{
Debug.WriteLine (entry.Message) ;
}
--
-----------
Thanks,
Steve
Comment