Page 25 of 92

Re: EPG123 Bug Reports

Posted: Fri Sep 30, 2016 1:54 pm
by Scallica
The disappearing channels issue should be discussed here:

http://www.thegreenbutton.tv/forums/vie ... 99&t=10381

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 12:01 am
by chupon
Not sure if this is epg123 or schedules direct

My guide data for fox isn't right. World series is not showing, instead it's repeats of their Tuesday night shows.

Any ideas?

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 1:57 am
by garnuts
chupon wrote:Not sure if this is epg123 or schedules direct

My guide data for fox isn't right. World series is not showing, instead it's repeats of their Tuesday night shows.

Any ideas?
Same for me in Columbus, OH. (cable not OTA)

I checked with Schedules Direct, and they emailed me back with a copy of the guide data on their end and this comment:

"The extract that I sent you was from the server that gives EPG123 its data, and you saw that the game was there. I'm not sure how you force EPG123 to flush its cache, but it seems to have stale data"

Is there a way to force EPG123 to flush it's cache?

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 2:29 am
by rkulagow
I sent garyan2 the raw JSON for garnuts' issue.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 2:45 am
by fzy8gc
For further conformation, I checked my guide for Fox 13 Tampa at 10:38 pm EDT. It shows no World Series for Tuesday at 10:38 pm or Wednesday any time. When I did a Title search all I could find was "2016 World Series of Poker". The World Series is playing live on that channel.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 3:18 am
by rkulagow
If you're having an issue with the guide, please open a ticket at the Schedules Direct website and I can pull the raw lineup information.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 3:33 am
by garyan2
This is not a EPG123 cache problem, it is a WMC import issue that we haven't quite found a good way to handle yet. When loadmxf.exe (MS tool) imports the epg123.mxf file into WMC, it goes through some logic that tends to be ultra conservative (risk averse) and will not update the guide listings if it believes what already exists should stay. There has been no reliable way to convince it otherwise ... yet.

There are a couple ways to try to kick it ...

1) If you use automatch, use the epg123 GUI to deselect (remove) the station that will not update. Save&Execute and allow it to import and index. Re-add the channel in the GUI and Save&Execute again. The channel should be completely refreshed with current data.

2) Reboot into safe mode and use the [Rebuild Database] button. This will delete your current database, create a new database, import the tuner channels, import your scheduled recordings, and import the current listings. There is some risk that this method will fail, so I recommend backing up first. I also recommend running epg123 again after reboot to kick off the reindex.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 1:30 pm
by schottjy
I've had success just rerunning TV Setup and declining then terms of service (again) and then running epg123. My series recordings and one time recordings have been preserved when I've tried this.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 5:51 pm
by garnuts
RE: World Series on Fox guide data

Today's game (Wed 11/2) is correct 8-11pm EST. However the 30 minute Pregame show is not correct.

Whereas yesterday it was reversed. The Pregame show was correct in the guide but the game wasn't.

At least tonight when I record the game it will not be broken into 4 separate recordings like last night.

Thanks for a possible workaround garyan2, but I won't need it tonight.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 6:18 pm
by fzy8gc
garnuts wrote:RE: World Series on Fox guide data

Today's game (Wed 11/2) is correct 8-11pm EST. However the 30 minute Pregame show is not correct.

Whereas yesterday it was reversed. The Pregame show was correct in the guide but the game wasn't.

At least tonight when I record the game it will not be broken into 4 separate recordings like last night.

Thanks for a possible workaround garyan2, but I won't need it tonight.
FYI...As long as you know about it ahead of time, you also can always do a manual record when the guide is incorrect.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 10:15 pm
by audinutt
Mine won't update, already cleared the cache folder twice, didn't change anything... it worked last night...

here's the tracelog
[11/2/2016 5:13:56 PM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 14 , PrefixEpisodeTitle: True , AppendEpisodeDesc: False , AutoImport: True , TMDbCoverArt: True , LogoOverride: True , Automatch: True , AutoAddNew: True
[11/2/2016 5:13:56 PM] [ INFO] Successfully retrieved TMDb configurations.
[11/2/2016 5:13:56 PM] [ INFO] Token request successful. serverID: 20141201.web.2
[11/2/2016 5:13:56 PM] [ INFO] epg123 is up to date. version: 1.0.2
[11/2/2016 5:13:56 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/2/2016 5:13:56 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-TX64967-X.
[11/2/2016 5:13:56 PM] Entering getAllScheduleEntryMd5s() for 14 days on 201 stations.
[11/2/2016 5:13:58 PM] [ INFO] Successfully retrieved Md5s for 201 station's daily schedules.
[11/2/2016 5:13:59 PM] [ INFO] Successfully retrieved 4 station's daily schedules.
[11/2/2016 5:14:00 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[11/2/2016 5:14:00 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[11/2/2016 5:14:00 PM] [ERROR] Failed to create MXF file. Exiting.
[11/2/2016 5:14:00 PM] [STATS] epg123 update execution time was 00:00:04.1850117.

Re: EPG123 Bug Reports

Posted: Wed Nov 02, 2016 11:24 pm
by jonwz
I'm also seeing this...

[11/2/2016 5:14:00 PM] [ERROR] Did not find expected Md5Schedule file in cache directory.
[11/2/2016 5:14:00 PM] [ERROR] Problem occurred during processMd5ScheduleEntry().
[11/2/2016 5:14:00 PM] [ERROR] Failed to create MXF file. Exiting.
[11/2/2016 5:14:00 PM] [STATS] epg123 update execution time was 00:00:04.1850117.

...on the system I tried removing the world series channel and then adding it back. I can only get that channel back from a "re-signal", that gives me all the channels from mcupdate.

I got in this situation from trying Gary's suggestion at:

1) If you use automatch, use the epg123 GUI to deselect (remove) the station that will not update. Save&Execute and allow it to import and index. Re-add the channel in the GUI and Save&Execute again. The channel should be completely refreshed with current data.

I guess the "good" news is that the guide from mcupdate also didn't reflect the guide change. So I think as Gary says, this is probably a 7mc problem.

Since 7mc is dead code, I hope Gary can figure out how to circumvent.

But my immediate problem is that EPG123 won't restore the channel that I deleted (1013). How can I fix that?

Re: EPG123 Bug Reports

Posted: Thu Nov 03, 2016 1:54 am
by garyan2
There's another thread created for this problem here... here's my response.
garyan2 wrote: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.

Re: EPG123 Bug Reports

Posted: Thu Nov 03, 2016 2:14 am
by fzy8gc
This may make you feel better. TiVo's guide also did not have the World Series listed for tonight. I had to add 3 hours to "Lethal Weapon" to record it. Of course, I am sure you know ROVI is now associated with TiVo.

Re: EPG123 Bug Reports

Posted: Wed Nov 16, 2016 2:53 pm
by glorp
I'm getting hundreds of these type messages in the trace.log during the data pull from a few hours ago. On previous instances of these type ALERTs, the answer was that these are caused by EPG123 failing to retrieve schedule data for those named channels after the date mentioned. The channels should still be in the lineup so I'm guessing this is entirely related to the S-D issues that some had already noted here starting yesterday. I've opened a ticket about it at S-D just in case. It appears to be almost exclusively SD channels in the lineup affected but I note that the .mxf which was generated is a fraction of it's normal size so I shut off client MXF file loads for now. Any other steps that should be taken Gary?

Code: Select all

[11/16/2016 6:01:38 AM] [ALERT] Failed to parse the schedule Md5 return for stationId 10161 (CSPAN) on 2016-11-16 and after. message: Accessed JArray values with invalid key value: "2016-11-16". Int32 array index expected.
[11/16/2016 6:01:38 AM] [ALERT] Failed to parse the schedule Md5 return for stationId 10162 (CSPAN2) on 2016-11-16 and after. message: Accessed JArray values with invalid key value: "2016-11-16". Int32 array index expected.

Re: EPG123 Bug Reports

Posted: Wed Nov 16, 2016 11:47 pm
by garyan2
glorp wrote:I'm getting hundreds of these type messages in the trace.log during the data pull from a few hours ago. On previous instances of these type ALERTs, the answer was that these are caused by EPG123 failing to retrieve schedule data for those named channels after the date mentioned. The channels should still be in the lineup so I'm guessing this is entirely related to the S-D issues that some had already noted here starting yesterday. I've opened a ticket about it at S-D just in case. It appears to be almost exclusively SD channels in the lineup affected but I note that the .mxf which was generated is a fraction of it's normal size so I shut off client MXF file loads for now. Any other steps that should be taken Gary?

Code: Select all

[11/16/2016 6:01:38 AM] [ALERT] Failed to parse the schedule Md5 return for stationId 10161 (CSPAN) on 2016-11-16 and after. message: Accessed JArray values with invalid key value: "2016-11-16". Int32 array index expected.
[11/16/2016 6:01:38 AM] [ALERT] Failed to parse the schedule Md5 return for stationId 10162 (CSPAN2) on 2016-11-16 and after. message: Accessed JArray values with invalid key value: "2016-11-16". Int32 array index expected.
These errors are due to Schedules Direct returning an empty array of listings for that station on that day. If I encounter it, I just stop trying for that station entirely.

Allowing the client MXF loads causes no issues in this case. Since the station is still a part of the lineup, no harm is done. That station just doesn't have any updated information.

Re: EPG123 Bug Reports

Posted: Thu Nov 17, 2016 3:29 pm
by rwsorden
A strange thing is happening today with my channel lineup. I have two WMC HTPCs: one Windows 7 and one Windows 8.1. Both are running the latest EPG123 v1.02 with the same exact configuration (different scheduled task times). My channel lineup is USA-IL12549-X (zip code 62221).

On Windows 8.1, EPG123 is failing today when it executes with the following error:

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at epg123.sdJson2mxf.buildAllGenericSeriesInfoDescriptions()
at epg123.sdJson2mxf..ctor(epgConfig config)
at epg123.Program.Main(String[] args)

The scheduled task exits with exit code 0xC0000005.

On Windows 7, on the other hand, EPG123 is running without any noticable failure. However, all channel lineup data is missing for all of the channels between 181 and 937.

Per Schedules Direct, the channel lineup report looks correct.

Here is the log file from the Windows 8.1 system:

Code: Select all

[11/17/2016 8:34:02 AM] ===============================================================================
[11/17/2016 8:34:02 AM]  Activating the epg123 configuration GUI.
[11/17/2016 8:34:02 AM] ===============================================================================
[11/17/2016 8:34:03 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 8:34:05 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 8:34:05 AM] [ INFO] Status request successful. account expires: 2017-09-29T11:11:40Z , lineups: 1/4 , lastDataUpdate: 2016-11-17T13:57:59Z
[11/17/2016 8:34:05 AM] [ INFO] system status: Online , message: No known issues.
[11/17/2016 8:34:05 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:06 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:34:06 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 11/17/2016 4:00:00 AM; Exit: 0xC0000005
[11/17/2016 8:34:08 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:15 AM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[11/17/2016 8:34:23 AM] [ INFO] Successfully retrieved the headends for USA and postal code 62221.
[11/17/2016 8:34:32 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:32 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:38:29 AM] ===============================================================================
[11/17/2016 8:38:29 AM]  Beginning epg123 update execution.
[11/17/2016 8:38:29 AM] ===============================================================================
[11/17/2016 8:38:29 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[11/17/2016 8:38:29 AM] [ INFO] Successfully retrieved TMDb configurations.
[11/17/2016 8:38:29 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 8:38:29 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 8:38:30 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:38:30 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:38:30 AM] Entering getAllScheduleEntryMd5s() for 30 days on 172 stations.
[11/17/2016 8:38:32 AM] [ INFO] Successfully retrieved Md5s for 172 station's daily schedules.
[11/17/2016 8:38:37 AM] [ INFO] Successfully retrieved 172 station's daily schedules.
[11/17/2016 8:38:56 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[11/17/2016 8:38:56 AM] Entering buildAllProgramEntries() for 34882 programs.
[11/17/2016 8:41:00 AM] [ INFO] Successfully retrieved 748 programs metadata.
[11/17/2016 8:41:03 AM] Exiting buildAllProgramEntries(). SUCCESS.
[11/17/2016 8:41:03 AM] Entering buildAllGenericSeriesInfoDescriptions() for 5594 series.
[11/17/2016 9:00:25 AM] ===============================================================================
[11/17/2016 9:00:25 AM]  Activating the epg123 configuration GUI.
[11/17/2016 9:00:25 AM] ===============================================================================
[11/17/2016 9:00:26 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 9:00:29 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 9:00:30 AM] [ INFO] Status request successful. account expires: 2017-09-29T11:11:40Z , lineups: 1/4 , lastDataUpdate: 2016-11-17T13:57:59Z
[11/17/2016 9:00:30 AM] [ INFO] system status: Online , message: No known issues.
[11/17/2016 9:00:30 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 9:00:30 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 9:00:30 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 11/17/2016 4:00:00 AM; Exit: 0xC0000005

Re: EPG123 Bug Reports

Posted: Thu Nov 17, 2016 6:20 pm
by Scallica
^Duplicate post deleted. Use code tags when including log files.

Re: EPG123 Bug Reports

Posted: Thu Nov 17, 2016 8:32 pm
by glorp
garyan2 wrote:These errors are due to Schedules Direct returning an empty array of listings for that station on that day. If I encounter it, I just stop trying for that station entirely.
I got an email from S-D about an hour after opening my ticket there indicating they had been rebuilding schedules after the db dump from the prior day. My scheduling for the update task often seems to hit maintenance periods for them so I may need to rethink my timings of it. Anyway, all was back to normal by the time the email was received and back to normal processing without additional intervention the next update cycle. Thanks for the input.

Re: EPG123 Bug Reports

Posted: Thu Nov 17, 2016 8:48 pm
by rwsorden
rwsorden wrote:A strange thing is happening today with my channel lineup. I have two WMC HTPCs: one Windows 7 and one Windows 8.1. Both are running the latest EPG123 v1.02 with the same exact configuration (different scheduled task times). My channel lineup is USA-IL12549-X (zip code 62221).

On Windows 8.1, EPG123 is failing today when it executes with the following error:

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at epg123.sdJson2mxf.buildAllGenericSeriesInfoDescriptions()
at epg123.sdJson2mxf..ctor(epgConfig config)
at epg123.Program.Main(String[] args)

The scheduled task exits with exit code 0xC0000005.

On Windows 7, on the other hand, EPG123 is running without any noticable failure. However, all channel lineup data is missing for all of the channels between 181 and 937.

Per Schedules Direct, the channel lineup report looks correct.

Here is the log file from the Windows 8.1 system:

Code: Select all

[11/17/2016 8:34:02 AM] ===============================================================================
[11/17/2016 8:34:02 AM]  Activating the epg123 configuration GUI.
[11/17/2016 8:34:02 AM] ===============================================================================
[11/17/2016 8:34:03 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 8:34:05 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 8:34:05 AM] [ INFO] Status request successful. account expires: 2017-09-29T11:11:40Z , lineups: 1/4 , lastDataUpdate: 2016-11-17T13:57:59Z
[11/17/2016 8:34:05 AM] [ INFO] system status: Online , message: No known issues.
[11/17/2016 8:34:05 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:06 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:34:06 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 11/17/2016 4:00:00 AM; Exit: 0xC0000005
[11/17/2016 8:34:08 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:15 AM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[11/17/2016 8:34:23 AM] [ INFO] Successfully retrieved the headends for USA and postal code 62221.
[11/17/2016 8:34:32 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:34:32 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:38:29 AM] ===============================================================================
[11/17/2016 8:38:29 AM]  Beginning epg123 update execution.
[11/17/2016 8:38:29 AM] ===============================================================================
[11/17/2016 8:38:29 AM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 30 , PrefixEpisodeTitle: True , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[11/17/2016 8:38:29 AM] [ INFO] Successfully retrieved TMDb configurations.
[11/17/2016 8:38:29 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 8:38:29 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 8:38:30 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 8:38:30 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 8:38:30 AM] Entering getAllScheduleEntryMd5s() for 30 days on 172 stations.
[11/17/2016 8:38:32 AM] [ INFO] Successfully retrieved Md5s for 172 station's daily schedules.
[11/17/2016 8:38:37 AM] [ INFO] Successfully retrieved 172 station's daily schedules.
[11/17/2016 8:38:56 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[11/17/2016 8:38:56 AM] Entering buildAllProgramEntries() for 34882 programs.
[11/17/2016 8:41:00 AM] [ INFO] Successfully retrieved 748 programs metadata.
[11/17/2016 8:41:03 AM] Exiting buildAllProgramEntries(). SUCCESS.
[11/17/2016 8:41:03 AM] Entering buildAllGenericSeriesInfoDescriptions() for 5594 series.
[11/17/2016 9:00:25 AM] ===============================================================================
[11/17/2016 9:00:25 AM]  Activating the epg123 configuration GUI.
[11/17/2016 9:00:25 AM] ===============================================================================
[11/17/2016 9:00:26 AM] [ INFO] epg123 is up to date. version: 1.0.2
[11/17/2016 9:00:29 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[11/17/2016 9:00:30 AM] [ INFO] Status request successful. account expires: 2017-09-29T11:11:40Z , lineups: 1/4 , lastDataUpdate: 2016-11-17T13:57:59Z
[11/17/2016 9:00:30 AM] [ INFO] system status: Online , message: No known issues.
[11/17/2016 9:00:30 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[11/17/2016 9:00:30 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-IL12549-X.
[11/17/2016 9:00:30 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 11/17/2016 4:00:00 AM; Exit: 0xC0000005
Got a response from Schedules Direct that indicated a lineup rebuild. That fixed the issue I was having.