Md5 Mismatches and EventLog Error

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
User avatar
garyan2

Posts: 7438
Joined: Fri Nov 27, 2015 7:23 pm
Location:

HTPC Specs: Show details

Md5 Mismatches and EventLog Error

#1

Post by garyan2 » Wed Mar 01, 2017 5:58 am

A lot of people may be noticing an error in their trace.log file like the below. If you look in the Event Viewer and find the EPG123 Warning entry, you will see many, many, many Md5 mismatches listed (or listed in the trace.log file if not using v1.1.x). In this particular case, I believe this is due to some new features SD has rolled out concerning images (series, episode, movie, sports). Part of the new feature was to add additional flags to the program response which changed the Md5 of the entire program ... leading to a mismatch.

EDIT: Just got notified by SD that there was some server outage earlier today and the errors are temporary while everything tries to catch back up.
http://www.usatoday.com/story/tech/news ... /98530914/
[ERROR] WritingEventLog Failed with System.ArgumentException: Log entry string is too long. A string written to the event log cannot exceed 32766 characters.
at System.Diagnostics.EventLogInternal.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
at System.Diagnostics.EventLogInternal.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at epg123.EventLogger.InsertEventLog(EventLogEntryType evtLogType, String strMsg)
I believe I will stop reporting the mismatches altogether. There has never been any actionable meaning to the reporting, and there is no evidence the mismatch means the data is corrupted. It is barely at the FYI level, so I"m going to drop it.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
12noon

Posts: 127
Joined: Mon Oct 06, 2014 4:23 pm
Location:

HTPC Specs: Show details

#2

Post by 12noon » Wed Mar 01, 2017 4:12 pm

Excellent. Thanks for the info! :)
USA 60005
WOW Chicago Suburbs - Digital
USA-IL58819-X

Post Reply