TheGreenButton - Windows Media Center Forums

First - thanks for the epg123 utility, it's been working great the last 2 months for me. Ran into an issue today though - getting the following error: "Did not find expected Md5Schedule file in cache directory. Failed to create MXF file. Exiting"

The timing on this is terrible as my guide didn't update to record game 7 of World Series . I can upload the complete log file later if that would help. Already tried deleting the cache folder. I'm using v1.0.0 (newer versions showed up as Trojans when I originally installed). Any help would be appreciated. Thanks!

This is an issue with Schedules Direct and has to do with a MD5 mismatch between what a schedule entry identifies a programs MD5 is versus what the downloaded program self declares its MD5 is. Unfortunately I'm not able to help in identifying which service/program it is, so the best I can suggest is to open a ticket with SD.

Note to self: Find a way to allow epg123 to build a mxf file with a 'gap' in the schedule due to this error.

Thanks for the quick reply. I'll open a ticket with SD.

Just thought of something you could do... there is no telling which program on which service on which day your wayward MD5 problem is, but what you could do is direct epg123 to only download a single days worth of schedule. This way, if the problem child not in today's listings, but is sometime in the future, then you won't receive the error and epg123 will successfully run. You will at least get the rest of today's and most of tomorrow's listings updated.

I will go through the schedule assembly code on the server to determine why you're seeing different MD5's. You're saying that the schedule says that the MD5 is foo, but when you download the program it has an MD5 of bar?

rkulagow wrote:I will go through the schedule assembly code on the server to determine why you're seeing different MD5's. You're saying that the schedule says that the MD5 is foo, but when you download the program it has an MD5 of bar?

Correct. This has happened a few times in the past, but I'm having a senior moment and can't remember what was done on your end to correct it.

Just to follow up, guide update worked properly today. Thank you again for the quick replies.