TheGreenButton - Windows Media Center Forums

Posted: **Sat Oct 29, 2016 9:33 pm**

So far we're good. I have it set to 16 days of data so that it will maintain a solid 2 weeks. It hasn't dropped below 14 days since I refreshed the auto execute.

Sent from my VS986 using Tapatalk

Posted: **Sun Apr 16, 2017 2:41 pm**

garyan2,

Hate to bring it up again, but the dreaded "Did not find expected Md5Schedule file in cache directory." bug appears to still be happening in 1.1.4 (tracelog below).

Code: Select all

[4/16/2017 2:44:30 AM] ===============================================================================
[4/16/2017 2:44:30 AM]  Activating the epg123 configuration GUI.
[4/16/2017 2:44:30 AM] ===============================================================================
[4/16/2017 2:44:55 AM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 2:44:55 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready.The task has not yet run. Exit: 0x00000001.
[4/16/2017 2:44:55 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 2:44:55 AM] [ INFO] Status request successful. account expires: 2017-09-26T18:49:00Z , lineups: 1/4 , lastDataUpdate: 2017-04-16T01:21:11Z
[4/16/2017 2:44:55 AM] [ INFO] system status: Online , message: No known issues.
[4/16/2017 2:44:55 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 2:44:55 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CT06421-X.
[4/16/2017 2:45:01 AM] ===============================================================================
[4/16/2017 2:45:01 AM]  Beginning epg123 update execution.
[4/16/2017 2:45:01 AM] ===============================================================================
[4/16/2017 2:45:01 AM] [ INFO] Successfully retrieved TMDb configurations.
[4/16/2017 2:45:01 AM] [ INFO] epg123 version 1.1.4 , DaysToDownload: 30 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , TMDbCoverArt: True , LogoOverride: True , AutoAddNew: True
[4/16/2017 2:45:02 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[4/16/2017 2:45:02 AM] [ INFO] epg123 is up to date. version: 1.1.4
[4/16/2017 2:45:02 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[4/16/2017 2:45:02 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CT06421-X.
[4/16/2017 2:45:02 AM] Entering getAllScheduleEntryMd5s() for 30 days on 178 stations.
[4/16/2017 2:45:05 AM] [ INFO] Successfully retrieved Md5s for 178 station's daily schedules.
[4/16/2017 2:45:06 AM] [ INFO] Successfully retrieved 23 station's daily schedules.
[4/16/2017 2:45:06 AM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[4/16/2017 2:45:06 AM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[4/16/2017 2:45:06 AM] [ERROR] Failed to create MXF file. Exiting.
[4/16/2017 2:45:06 AM] [STATS] epg123 update execution time was 00:00:04.6812238.

I had some an unrelated issue that required resetting my Ceton infiniTV6, but when I got to adding my listings that's where things went sideways.
Things that are common in all of these attempts below: running as Administrator, and the Scheduled Task was deleted ahead of the first upgrade.

Initially, I was on version 1.0.2 (was working fine until last night), and watching the command window saw it crash somewhere on the second step. (Didn't check my tracelog on that run, but since that's the same point where it fails later I'm assuming I'd have seen the same as later runs.)
I had noticed the message that there was a new version out, so I grabbed version 1.1.3 and the upgrade utility, ran the utility copied over the 1.1.3 files, and tried again. Same result; also this is the point where I started paying attention to the tracelog.
I tried doing a clean install of version 1.1.3, using the Clean Start method; same result.
I repeated that process doing the Clean Start the old way (via a backup copy of 1.0.2, then using 1.1.3); same result.
I went back into try something else (I forget what), and got the notice that 1.1.4 was now available, downloaded it.
So far, I've attempted all the same things I'd done with 1.1.3 in 1.1.4, and even tried copying over my backup of the cache from 1.0.2; still no joy.

Suggestions?

Posted: **Sun Apr 16, 2017 2:56 pm**

For epg123, it's not a bug if it is what I intended to do when there is a problem with the Schedules Direct responses. In this case, I haven't designed a method to handle/recover from the Md5 mismatches of the schedule entries. I can do it no problem with the program entries, but I am limited on options with the schedule entries due to the structure of my code.

Right now, my only advice is to have patience and allow Schedules Direct to fix the issue (probably rebuild some databases).

Posted: **Mon Apr 17, 2017 3:11 am**

Thanks for that...

Now wishing I'd seen this before my other post to the 1.1.4 thread. DOH!
Am I understanding correctly, that the various JSON issues recently are a known problem on SD's end?
(Seems like a common response, from the bits and pieces I've understood so far, which admittedly isn't a lot.)

Posted: **Mon Apr 17, 2017 3:22 am**

Illinger wrote:Thanks for that...

Now wishing I'd seen this before my other post to the 1.1.4 thread. DOH!
Am I understanding correctly, that the various JSON issues recently are a known problem on SD's end?
(Seems like a common response, from the bits and pieces I've understood so far, which admittedly isn't a lot.)

Yah, I think these issues all started Friday when the feed to Schedules Direct unexpectedly changed their API causing issues down the line to us. It looks like the recovery from that error was not complete or maybe caused some other issues for us starting last night and still ongoing.

We're working on it.

Posted: **Mon Apr 17, 2017 4:33 am**

This issue (de-serialization error) has been fixed. Please open a ticket at Schedules Direct if you're continuing to see errors.

Posted: **Mon Apr 24, 2017 9:01 pm**

garyan2 wrote:
Illinger wrote:Thanks for that...

Now wishing I'd seen this before my other post to the 1.1.4 thread. DOH!
Am I understanding correctly, that the various JSON issues recently are a known problem on SD's end?
(Seems like a common response, from the bits and pieces I've understood so far, which admittedly isn't a lot.)
Yah, I think these issues all started Friday when the feed to Schedules Direct unexpectedly changed their API causing issues down the line to us. It looks like the recovery from that error was not complete or maybe caused some other issues for us starting last night and still ongoing.

We're working on it.

Just wondering; How long will you keep supporting epg123, Gary? We need this for continued use of WMC going forward..

Thanks!

Posted: **Tue Apr 25, 2017 12:54 am**

Sammy2 wrote:Just wondering; How long will you keep supporting epg123, Gary? We need this for continued use of WMC going forward..

I keep thinking I'll reach the end of development and into sustainment to just keep up with API changes that will come... but keep finding things to improve on and features to add!

Ultimately, I'm around for a long time because remember ... I'm not just the president of EPG123, I'm also a client!

TheGreenButton - Windows Media Center Forums

EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data

Re: EPG123 - Down to 3 days of guide data