EPG123 error

[tfellenbaum]

I have been using EPG123 for a good 5 or 6 months now without any issues, But on my last update Epg123 has been giving a message that it has stopped working. This is more like windows telling me that epg123 has stopped working. It always happens right after the seconds set of numbers counts all the way up. My computer had crashed during a guide update could this be why its no longer working. Believe it or not my computer crashed because of a bad connection between my pc and my fathers flip phone

[kmp14]

You would be better served to post this in the EPG123 Sub-forum: http://www.thegreenbutton.tv/forums/viewforum.php?f=99

[STC]

moved

[glorp]

Me too. A second, manual run about 15 minutes later worked fine. Think something was wrong with SD or else channels had been moved around and I needed to run GUI first. Section of log:

Code: Select all

[1/19/2017 6:00:00 AM] ===============================================================================
[1/19/2017 6:00:00 AM]  Beginning epg123 update execution.
[1/19/2017 6:00:00 AM] ===============================================================================
[1/19/2017 6:00:01 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 14 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , AutoImport: False , TMDbCoverArt: False , LogoOverride: False , Automatch: False , AutoAddNew: True
[1/19/2017 6:00:03 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[1/19/2017 6:00:03 AM] [ INFO] epg123 is up to date. version: 1.0.2
[1/19/2017 6:00:04 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[1/19/2017 6:00:04 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-XXXXXX-X.
[1/19/2017 6:00:05 AM] Entering getAllScheduleEntryMd5s() for 14 days on 520 stations.
[1/19/2017 6:00:48 AM] [ INFO] Successfully retrieved Md5s for 520 station's daily schedules.
[1/19/2017 6:01:46 AM] [ INFO] Successfully retrieved 520 station's daily schedules.
[1/19/2017 6:03:40 AM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[1/19/2017 6:03:40 AM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[1/19/2017 6:03:40 AM] [ERROR] Failed to create MXF file. Exiting.
[1/19/2017 6:03:40 AM] [STATS] epg123 update execution time was 00:03:38.7467298.

[garyan2]

Looks like we have had some more Md5 mismatches from SD. We are actively working on a solution, and I already have a work-around in the upcoming version... mismatches will no longer be an issue in v1.1.0 and above.