Is this a problem with EPG123 or SD?

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
Post Reply
DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

Is this a problem with EPG123 or SD?

#1

Post by DSperber » Fri Sep 11, 2020 12:23 pm

I have two Win7 HTPC's, both configured identically. Both use EPG123 1.3.10 and my SD subscription with two channel lineups (one for Spectrum cable, the other for OTA/ATSC).

One HTPC is working normally and EPG123 is working normally on that PC. But EPG123 apparently stopped working three days ago on the other PC. Last successful nightly update was early morning 9/7 at 5:18AM. My regular scheduled update is at 2AM, but apparently I must have been working on channel lineups and performed a manual update (or two) at around 5AM. Anyway, this all seemed to work fine per the log.

Then, apparently on the next normal nightly 2AM update of 9/8, something went wrong. From the log It looks like the update actually got started but doesn't seem to have done everything it should have. After a very abbreviated run it seems to have ended without any error messages. But most of the normally expected output is not present in the log.

And then, apparently, the last three nights EPG123 has apparently failed to even start, throwing some kind of a connection/login error to SD. There is nothing in the log for the past three nights. When I manually try to start EPG123 I get the following (several of my unsuccessful EPG123 launches just now do appear in the log):

Image

The EPG123 icon in the system tray is red. Hovering the mouse over it gets the flyout text about "last update was more than 24 hours ago" and provides the date/time of that update from back on 9/7.

Here is the end of my log, starting with thw last two successful nightly 2AM updates of both 9/6 and 9/7, as well as my 5AM manual update of 9/7. Apparently everything after that (starting with the 2AM update of 9/8) is some kind of indication of whatever problem is currently happening. I've just re-run the EPG123 1.3.10 installer, just to be sure everything is normal. This didn't clear up the issue and EPG123.exe still will not start, throwing that same error about failure to get a token from SD.

Code: Select all

[9/6/2020 2:00:00 AM] ===============================================================================
[9/6/2020 2:00:00 AM]  Beginning epg123 update execution. version 1.3.5.0
[9/6/2020 2:00:00 AM] ===============================================================================
[9/6/2020 2:00:00 AM] [ INFO] Beginning EPG123 update execution. 2020-09-06 09:00:00Z
[9/6/2020 2:00:00 AM] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : True , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[9/6/2020 2:00:01 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/6/2020 2:00:01 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-06T01:25:52Z
[9/6/2020 2:00:01 AM] [ INFO] system status: Online , message: No known issues.
[9/6/2020 2:00:02 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.10 and can be downloaded from http://epg123.garyan2.net.
[9/6/2020 2:00:02 AM] [ INFO] Successfully retrieved TMDb configurations.
[9/6/2020 2:00:02 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/6/2020 2:00:02 AM] Entering buildLineupServices() for 2 lineups.
[9/6/2020 2:00:03 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/6/2020 2:00:03 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/6/2020 2:00:03 AM] Exiting buildLineupServices(). SUCCESS.
[9/6/2020 2:00:03 AM] Entering getAllScheduleEntryMd5s() for 21 days on 92 stations.
[9/6/2020 2:00:14 AM] [ INFO] Successfully retrieved Md5s for  92 station's daily schedules. (0:00:00:11.2788001 /   166.360 KB)
[9/6/2020 2:00:19 AM] [ INFO] Successfully retrieved  56 station's daily schedules.          (0:00:00:04.6956000 /   890.728 KB)
[9/6/2020 2:00:20 AM] [ INFO] Found 1384 cached daily schedules.
[9/6/2020 2:00:20 AM] [ INFO] Downloaded 180 daily schedules.
[9/6/2020 2:00:22 AM] [ INFO] Processed 1564 daily schedules for 92 stations.
[9/6/2020 2:00:22 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[9/6/2020 2:00:22 AM] Entering buildAllProgramEntries() for 17397 programs.
[9/6/2020 2:00:36 AM] [ INFO] Found 17193 cached program descriptions.
[9/6/2020 2:00:37 AM] [ INFO] Successfully retrieved  204 program descriptions. (0:00:00:01.5132000 /   434.332 KB)
[9/6/2020 2:00:37 AM] [ INFO] Processed 17397 program descriptions.
[9/6/2020 2:00:37 AM] Exiting buildAllProgramEntries(). SUCCESS.
[9/6/2020 2:00:38 AM] Entering buildAllGenericSeriesInfoDescriptions() for 2529 series.
[9/6/2020 2:00:39 AM] [ INFO] Found 2521 cached series descriptions.
[9/6/2020 2:00:39 AM] [ INFO] Successfully retrieved   8 generic program descriptions. (0:00:00:00.2028000 /     2.798 KB)
[9/6/2020 2:00:39 AM] [ INFO] Processed 2529 series descriptions.
[9/6/2020 2:00:39 AM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[9/6/2020 2:00:39 AM] Entering getAllMoviePosters() for 1531 movies.
[9/6/2020 2:00:39 AM] [ INFO] Successfully retrieved artwork info for   7 programs. (0:00:00:00.2184000 /    51.227 KB)
[9/6/2020 2:00:40 AM] [ INFO] Processed 1531 movie poster links.
[9/6/2020 2:00:40 AM] Exiting getAllMoviePosters(). SUCCESS.
[9/6/2020 2:00:40 AM] Entering getAllSeriesImages() for 2529 series.
[9/6/2020 2:00:40 AM] [ INFO] Found 2407 cached series image links.
[9/6/2020 2:00:41 AM] [ INFO] Successfully retrieved artwork info for 122 programs. (0:00:00:01.5444000 /     1.517 MB)
[9/6/2020 2:00:41 AM] [ INFO] Processed 2529 series image links.
[9/6/2020 2:00:41 AM] Exiting getAllSeriesImages(). SUCCESS.
[9/6/2020 2:00:41 AM] [ INFO] Completed compiling keywords and keyword groups.
[9/6/2020 2:00:42 AM] [ INFO] Completed save of the MXF file to "C:\EPG123\output\epg123.mxf".
[9/6/2020 2:00:42 AM] [ INFO] Completed save of image archive file to "C:\EPG123\guideImages.xml".
[9/6/2020 2:00:43 AM] [ INFO] 1395 files deleted from the cache directory during cleanup.
[9/6/2020 2:00:43 AM] [ INFO] Downloaded and processed     3.026 MB of data from Schedules Direct.
[9/6/2020 2:00:43 AM] [ INFO] Generated .mxf file contains 92 services, 2529 series, 17397 programs, and 33235 people with 3996 image links.
[9/6/2020 2:00:43 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[9/6/2020 2:00:43 AM] [ INFO] epg123 update execution time was 00:00:42.9156003.
[9/6/2020 2:00:45 AM] ===============================================================================
[9/6/2020 2:00:45 AM]  Beginning epg123 client execution. version 1.3.5.0
[9/6/2020 2:00:45 AM] ===============================================================================
[9/6/2020 2:00:45 AM] [ INFO] Beginning epg123 client execution. 2020-09-06 09:00:45Z
[9/6/2020 2:00:45 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[9/6/2020 2:00:45 AM] Entering importMxfFile() for file "c:\epg123\output\epg123.mxf"
[9/6/2020 2:01:14 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[9/6/2020 2:01:14 AM] Exiting importMxfFile(). SUCCESS.
[9/6/2020 2:01:17 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[9/6/2020 2:01:17 AM] [ INFO] Completed lineup refresh.
[9/6/2020 2:01:17 AM] Entering runWmcTask(ReindexSearchRoot)
[9/6/2020 2:01:17 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[9/6/2020 2:01:17 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[9/6/2020 2:01:17 AM] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[9/6/2020 2:01:17 AM] Entering runWmcTask(PvrScheduleTask)
[9/6/2020 2:01:17 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\PvrScheduleTask".
[9/6/2020 2:01:17 AM] [ INFO] Successfully started the PvrScheduleTask task. Exit code: 0
[9/6/2020 2:01:17 AM] Exiting runWmcTask(PvrScheduleTask). SUCCESS.
[9/6/2020 2:01:17 AM] [ INFO] Completed EPG123 client execution.
[9/6/2020 2:01:17 AM] [ INFO] EPG123 client execution time was 00:00:32.4168002.
[9/7/2020 2:00:00 AM] ===============================================================================
[9/7/2020 2:00:00 AM]  Beginning epg123 update execution. version 1.3.5.0
[9/7/2020 2:00:00 AM] ===============================================================================
[9/7/2020 2:00:00 AM] [ INFO] Beginning EPG123 update execution. 2020-09-07 09:00:00Z
[9/7/2020 2:00:00 AM] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : True , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[9/7/2020 2:00:01 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/7/2020 2:00:01 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 2:00:01 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 2:00:02 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.10 and can be downloaded from http://epg123.garyan2.net.
[9/7/2020 2:00:02 AM] [ INFO] Successfully retrieved TMDb configurations.
[9/7/2020 2:00:02 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 2:00:02 AM] Entering buildLineupServices() for 2 lineups.
[9/7/2020 2:00:03 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 2:00:03 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 2:00:03 AM] Exiting buildLineupServices(). SUCCESS.
[9/7/2020 2:00:03 AM] Entering getAllScheduleEntryMd5s() for 21 days on 92 stations.
[9/7/2020 2:00:13 AM] [ INFO] Successfully retrieved Md5s for  92 station's daily schedules. (0:00:00:10.3272000 /   166.371 KB)
[9/7/2020 2:00:19 AM] [ INFO] Successfully retrieved  92 station's daily schedules.          (0:00:00:05.3664001 /   954.278 KB)
[9/7/2020 2:00:19 AM] [ INFO] Found 1342 cached daily schedules.
[9/7/2020 2:00:19 AM] [ INFO] Downloaded 222 daily schedules.
[9/7/2020 2:00:21 AM] [ INFO] Processed 1564 daily schedules for 92 stations.
[9/7/2020 2:00:21 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[9/7/2020 2:00:21 AM] Entering buildAllProgramEntries() for 17212 programs.
[9/7/2020 2:00:33 AM] [ INFO] Found 16415 cached program descriptions.
[9/7/2020 2:00:39 AM] [ INFO] Successfully retrieved  797 program descriptions. (0:00:00:05.4600000 /     1.460 MB)
[9/7/2020 2:00:40 AM] [ INFO] Processed 17212 program descriptions.
[9/7/2020 2:00:40 AM] Exiting buildAllProgramEntries(). SUCCESS.
[9/7/2020 2:00:40 AM] Entering buildAllGenericSeriesInfoDescriptions() for 2523 series.
[9/7/2020 2:00:42 AM] [ INFO] Found 2464 cached series descriptions.
[9/7/2020 2:00:42 AM] [ INFO] Successfully retrieved  59 generic program descriptions. (0:00:00:00.4368000 /    14.021 KB)
[9/7/2020 2:00:42 AM] [ INFO] Processed 2523 series descriptions.
[9/7/2020 2:00:42 AM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[9/7/2020 2:00:42 AM] Entering getAllMoviePosters() for 1518 movies.
[9/7/2020 2:00:43 AM] [ INFO] Successfully retrieved artwork info for  33 programs. (0:00:00:00.4524000 /   227.663 KB)
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "The Juniper Tree" from 1991 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "The Juniper Tree" from 1990 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Krane's Confectionery" from 1951 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Sinister Seduction" from 2019 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Husband's Secret Twin" from 2019 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Husband's Secret Twin" from 2018 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Husband's Secret Twin" from 2020 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Killer Twin" from 2018 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Was I Really Kidnapped?" from 2019 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Her Deadly Reflections" from 2020 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Daughter's Been Kidnapped" from 2020 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Daughter's Been Kidnapped" from 2019 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "My Daughter's Been Kidnapped" from 2021 found 0 results.
[9/7/2020 2:00:43 AM] [ INFO] TMDb catalog search for "Sacrifices of the Heart" from 2007 found 1 results.
[9/7/2020 2:00:43 AM] [ INFO] Processed 1518 movie poster links.
[9/7/2020 2:00:43 AM] Exiting getAllMoviePosters(). SUCCESS.
[9/7/2020 2:00:43 AM] Entering getAllSeriesImages() for 2523 series.
[9/7/2020 2:00:43 AM] [ INFO] Found 2358 cached series image links.
[9/7/2020 2:00:45 AM] [ INFO] Successfully retrieved artwork info for 165 programs. (0:00:00:01.6692000 /     1.565 MB)
[9/7/2020 2:00:45 AM] [ INFO] Processed 2523 series image links.
[9/7/2020 2:00:45 AM] Exiting getAllSeriesImages(). SUCCESS.
[9/7/2020 2:00:45 AM] [ INFO] Completed compiling keywords and keyword groups.
[9/7/2020 2:00:46 AM] [ INFO] Completed save of the MXF file to "C:\EPG123\output\epg123.mxf".
[9/7/2020 2:00:46 AM] [ INFO] Completed save of image archive file to "C:\EPG123\guideImages.xml".
[9/7/2020 2:00:47 AM] [ INFO] 1269 files deleted from the cache directory during cleanup.
[9/7/2020 2:00:47 AM] [ INFO] Downloaded and processed     4.355 MB of data from Schedules Direct.
[9/7/2020 2:00:47 AM] [ INFO] Generated .mxf file contains 92 services, 2523 series, 17212 programs, and 33056 people with 3964 image links.
[9/7/2020 2:00:47 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[9/7/2020 2:00:47 AM] [ INFO] epg123 update execution time was 00:00:46.5660003.
[9/7/2020 2:00:47 AM] ===============================================================================
[9/7/2020 2:00:47 AM]  Beginning epg123 client execution. version 1.3.5.0
[9/7/2020 2:00:47 AM] ===============================================================================
[9/7/2020 2:00:47 AM] [ INFO] Beginning epg123 client execution. 2020-09-07 09:00:47Z
[9/7/2020 2:00:47 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[9/7/2020 2:00:47 AM] Entering importMxfFile() for file "c:\epg123\output\epg123.mxf"
[9/7/2020 2:01:19 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[9/7/2020 2:01:19 AM] Exiting importMxfFile(). SUCCESS.
[9/7/2020 2:01:22 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[9/7/2020 2:01:22 AM] [ INFO] Completed lineup refresh.
[9/7/2020 2:01:22 AM] Entering runWmcTask(ReindexSearchRoot)
[9/7/2020 2:01:22 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[9/7/2020 2:01:22 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[9/7/2020 2:01:22 AM] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[9/7/2020 2:01:22 AM] Entering runWmcTask(PvrScheduleTask)
[9/7/2020 2:01:22 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\PvrScheduleTask".
[9/7/2020 2:01:22 AM] [ INFO] Successfully started the PvrScheduleTask task. Exit code: 0
[9/7/2020 2:01:22 AM] Exiting runWmcTask(PvrScheduleTask). SUCCESS.
[9/7/2020 2:01:22 AM] [ INFO] Completed EPG123 client execution.
[9/7/2020 2:01:22 AM] [ INFO] EPG123 client execution time was 00:00:34.8660003.
[9/7/2020 5:14:15 AM] ===============================================================================
[9/7/2020 5:14:15 AM]  Activating the epg123 configuration GUI. version 1.3.5.0
[9/7/2020 5:14:15 AM] ===============================================================================
[9/7/2020 5:14:17 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.10 and can be downloaded from http://epg123.garyan2.net.
[9/7/2020 5:14:17 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/7/2020 5:14:17 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 5:14:17 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 5:14:17 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 5:14:18 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 5:14:18 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 5:14:18 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 9/7/2020 2:00:00 AM; Exit: 0x00000000
[9/7/2020 5:15:08 AM] ===============================================================================
[9/7/2020 5:15:08 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/7/2020 5:15:08 AM] ===============================================================================
[9/7/2020 5:15:09 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/7/2020 5:15:10 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 5:15:10 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 5:15:10 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 5:15:10 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 5:15:11 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 5:15:11 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 9/7/2020 2:00:00 AM; Exit: 0x00000000
[9/7/2020 5:15:42 AM] ===============================================================================
[9/7/2020 5:15:42 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/7/2020 5:15:42 AM] ===============================================================================
[9/7/2020 5:15:43 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/7/2020 5:15:43 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 5:15:43 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 5:15:43 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 5:15:44 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 5:15:44 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 5:15:44 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 9/7/2020 2:00:00 AM; Exit: 0x00000000
[9/7/2020 5:17:07 AM] ===============================================================================
[9/7/2020 5:17:07 AM]  Beginning epg123 update execution. version 1.3.10.0
[9/7/2020 5:17:07 AM] ===============================================================================
[9/7/2020 5:17:07 AM] [ INFO] Beginning EPG123 update execution. 2020-09-07 12:17:07Z
[9/7/2020 5:17:07 AM] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : True , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[9/7/2020 5:17:07 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 5:17:07 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 5:17:08 AM] [ INFO] Successfully retrieved TMDb configurations.
[9/7/2020 5:17:08 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 5:17:08 AM] Entering buildLineupServices() for 2 lineups.
[9/7/2020 5:17:08 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 5:17:08 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 5:17:08 AM] Exiting buildLineupServices(). SUCCESS.
[9/7/2020 5:17:08 AM] Entering getAllScheduleEntryMd5s() for 21 days on 83 stations.
[9/7/2020 5:17:11 AM] [ INFO] Successfully retrieved Md5s for  83 station's daily schedules. (0:00:00:02.4200000 /   150.091 KB)
[9/7/2020 5:17:14 AM] [ INFO] Found 1411 cached daily schedules.
[9/7/2020 5:17:14 AM] [ INFO] Downloaded 0 daily schedules.
[9/7/2020 5:17:14 AM] [ INFO] Processed 1411 daily schedules for 83 stations.
[9/7/2020 5:17:14 AM] Exiting getAllScheduleEntryMd5s(). SUCCESS.
[9/7/2020 5:17:14 AM] Entering buildAllProgramEntries() for 15767 programs.
[9/7/2020 5:17:28 AM] [ INFO] Found 15767 cached program descriptions.
[9/7/2020 5:17:28 AM] [ INFO] Processed 15767 program descriptions.
[9/7/2020 5:17:28 AM] Exiting buildAllProgramEntries(). SUCCESS.
[9/7/2020 5:17:28 AM] Entering buildAllGenericSeriesInfoDescriptions() for 2228 series.
[9/7/2020 5:17:29 AM] [ INFO] Found 2228 cached series descriptions.
[9/7/2020 5:17:29 AM] [ INFO] Processed 2228 series descriptions.
[9/7/2020 5:17:29 AM] Exiting buildAllGenericSeriesInfoDescriptions(). SUCCESS.
[9/7/2020 5:17:29 AM] Entering getAllMoviePosters() for 1478 movies.
[9/7/2020 5:17:29 AM] [ INFO] Found 1478 cached movie poster links.
[9/7/2020 5:17:29 AM] [ INFO] Processed 1478 movie poster links.
[9/7/2020 5:17:29 AM] Exiting getAllMoviePosters(). SUCCESS.
[9/7/2020 5:17:29 AM] Entering getAllSeriesImages() for 2228 series.
[9/7/2020 5:17:29 AM] [ INFO] Found 0 cached series image links.
[9/7/2020 5:17:34 AM] [ INFO] Successfully retrieved artwork info for 500 programs. (0:00:00:05.0600000 /     9.941 MB)
[9/7/2020 5:17:34 AM] [ INFO] Successfully retrieved artwork info for 500 programs. (0:00:00:05.2900000 /    12.208 MB)
[9/7/2020 5:17:38 AM] [ INFO] Successfully retrieved artwork info for 500 programs. (0:00:00:08.7100000 /     7.477 MB)
[9/7/2020 5:17:39 AM] [ INFO] Successfully retrieved artwork info for 500 programs. (0:00:00:09.7700000 /     9.882 MB)
[9/7/2020 5:17:41 AM] [ INFO] Successfully retrieved artwork info for 228 programs. (0:00:00:05.8600000 /     4.501 MB)
[9/7/2020 5:17:42 AM] [ INFO] Processed 2228 series image links.
[9/7/2020 5:17:42 AM] Exiting getAllSeriesImages(). SUCCESS.
[9/7/2020 5:17:42 AM] [ INFO] Completed compiling keywords and keyword groups.
[9/7/2020 5:17:42 AM] [ INFO] Completed save of the MXF file to "C:\EPG123\output\epg123.mxf".
[9/7/2020 5:17:53 AM] [ INFO] 21299 files deleted from the cache directory during cleanup.
[9/7/2020 5:17:53 AM] [ INFO] 0 entries deleted from the cache file during cleanup.
[9/7/2020 5:17:54 AM] [ INFO] Downloaded and processed    44.155 MB of data from Schedules Direct.
[9/7/2020 5:17:54 AM] [ INFO] Generated .mxf file contains 84 services, 2228 series, 15767 programs, and 31921 people with 3635 image links.
[9/7/2020 5:17:54 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[9/7/2020 5:17:54 AM] [ INFO] epg123 update execution time was 00:00:47.
[9/7/2020 5:17:54 AM] ===============================================================================
[9/7/2020 5:17:54 AM]  Beginning epg123 client execution. version 1.3.10.0
[9/7/2020 5:17:54 AM] ===============================================================================
[9/7/2020 5:17:54 AM] [ INFO] Beginning epg123 client execution. 2020-09-07 12:17:54Z
[9/7/2020 5:17:54 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: True
[9/7/2020 5:17:55 AM] Entering importMxfFile() for file "c:\epg123\output\epg123.mxf"
[9/7/2020 5:18:39 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[9/7/2020 5:18:39 AM] Exiting importMxfFile(). SUCCESS.
[9/7/2020 5:18:40 AM] [ INFO] Removing HALLDR from channel 127 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:40 AM] [ INFO] Removing HEALTHHQ from channel 195 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:40 AM] [ INFO] Removing BNCP from channel 232 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:40 AM] [ INFO] Removing HEALTHHQ from channel 475 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:41 AM] [ INFO] Removing KIDSCHD from channel 917 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:41 AM] [ INFO] Removing HOGARHD from channel 940 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:41 AM] [ INFO] Removing KNBCDT3 from channel 1250 in lineup EPG123 Charter Spectrum - Digital (Hollywood).
[9/7/2020 5:18:43 AM] [ INFO] Removing KSCIDT9 from channel 20.1 in lineup EPG123 Local Over the Air Broadcast (90292).
[9/7/2020 5:18:43 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[9/7/2020 5:18:43 AM] [ INFO] Completed lineup refresh.
[9/7/2020 5:18:43 AM] Entering runWmcTask(ReindexSearchRoot)
[9/7/2020 5:18:43 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[9/7/2020 5:18:43 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[9/7/2020 5:18:43 AM] Exiting runWmcTask(ReindexSearchRoot). SUCCESS.
[9/7/2020 5:18:43 AM] [ INFO] MXF file was created on 9/7/2020 5:15:42 AM
[9/7/2020 5:18:43 AM] [ INFO] Completed EPG123 client execution.
[9/7/2020 5:18:43 AM] [ INFO] EPG123 client execution time was 00:00:48.3800000.
[9/7/2020 5:20:15 AM] ===============================================================================
[9/7/2020 5:20:15 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/7/2020 5:20:15 AM] ===============================================================================
[9/7/2020 5:20:16 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/7/2020 5:20:17 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-07T02:02:50Z
[9/7/2020 5:20:17 AM] [ INFO] system status: Online , message: No known issues.
[9/7/2020 5:20:17 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/7/2020 5:20:17 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/7/2020 5:20:18 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/7/2020 5:20:18 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 9/7/2020 2:00:00 AM; Exit: 0x00000000
[9/8/2020 2:00:03 AM] ===============================================================================
[9/8/2020 2:00:03 AM]  Beginning epg123 update execution. version 1.3.10.0
[9/8/2020 2:00:03 AM] ===============================================================================
[9/8/2020 2:00:03 AM] [ INFO] Beginning EPG123 update execution. 2020-09-08 09:00:03Z
[9/8/2020 2:00:03 AM] [ INFO] DaysToDownload: 21 , TheTVDBNumbers : True , PrefixEpisodeTitle: True , PrefixEpisodeDescription : True , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[9/8/2020 2:00:04 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[9/8/2020 2:00:05 AM] [ INFO] Status request successful. account expires: 2021-04-21T07:19:18Z , lineups: 2/4 , lastDataUpdate: 2020-09-08T03:03:27Z
[9/8/2020 2:00:05 AM] [ INFO] system status: Online , message: No known issues.
[9/8/2020 2:00:05 AM] [ INFO] Successfully retrieved TMDb configurations.
[9/8/2020 2:00:06 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[9/8/2020 2:00:06 AM] Entering buildLineupServices() for 2 lineups.
[9/8/2020 2:00:06 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA57315-X.
[9/8/2020 2:00:07 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-90292.
[9/8/2020 2:00:07 AM] Exiting buildLineupServices(). SUCCESS.
[9/8/2020 2:00:07 AM] Entering getAllScheduleEntryMd5s() for 21 days on 83 stations.
[9/8/2020 2:00:20 AM] ===============================================================================
[9/8/2020 2:00:20 AM]  Beginning epg123 client execution. version 1.3.10.0
[9/8/2020 2:00:20 AM] ===============================================================================
[9/8/2020 2:00:20 AM] [ INFO] Beginning epg123 client execution. 2020-09-08 09:00:20Z
[9/8/2020 2:00:20 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[9/8/2020 2:00:20 AM] Entering PerformGarbageCleanup().
[9/8/2020 2:14:40 AM] [ INFO] Successfully complete garbage cleanup. Exit code: 0
[9/8/2020 2:14:40 AM] Exiting PerformGarbageCleanup(). SUCCESS.
[9/11/2020 4:33:25 AM] ===============================================================================
[9/11/2020 4:33:25 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/11/2020 4:33:25 AM] ===============================================================================
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:26 AM] [ERROR] Did not receive a response from Schedules Direct for a version check.
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:26 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[9/11/2020 4:33:35 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 9/11/2020 4:00:00 AM; Exit: 0x80070002
[9/11/2020 4:33:58 AM] ===============================================================================
[9/11/2020 4:33:58 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/11/2020 4:33:58 AM] ===============================================================================
[9/11/2020 4:33:58 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:58 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:58 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:58 AM] [ERROR] Did not receive a response from Schedules Direct for a version check.
[9/11/2020 4:33:58 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:58 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:58 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[9/11/2020 4:34:05 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 9/11/2020 4:00:00 AM; Exit: 0x80070002
[9/11/2020 4:37:24 AM] ===============================================================================
[9/11/2020 4:37:24 AM]  Activating the epg123 client GUI. version 1.3.10.0
[9/11/2020 4:37:24 AM] ===============================================================================
[9/11/2020 4:37:24 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 9/11/2020 4:00:00 AM; Exit: 0x80070002
[9/11/2020 4:37:28 AM] [ INFO] Attempting to repair MergedChannel "20.1 : KSCIDT9 - DF2B08 = { (20.1 : KSCIDT9 - 2076C47) + [ 20.1 : SonLife - DF2AD5] }" by unsubscribing all non-scan lineup channels.
[9/11/2020 4:37:28 AM] [ INFO]    Failed to repair MergedChannel "20.1 : KSCIDT9 - DF2B08 = { (20.1 : KSCIDT9 - 2076C47) + [ 20.1 : SonLife - DF2AD5] }". Deleting channel.
[9/11/2020 4:54:45 AM] ===============================================================================
[9/11/2020 4:54:45 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/11/2020 4:54:45 AM] ===============================================================================
[9/11/2020 4:54:45 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:54:45 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:54:45 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:54:45 AM] [ERROR] Did not receive a response from Schedules Direct for a version check.
[9/11/2020 4:54:45 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:54:45 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:54:45 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[9/11/2020 4:56:49 AM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 9/11/2020 4:00:00 AM; Exit: 0x80070002
[9/11/2020 4:57:39 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:57:39 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:57:39 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
JUST NOTICED: Apparently on the problem PC I was still running version 1.3.5 of EPG123 back on 9/6. Looks like I must have noticed that and run the 1.3.10 installer as part of what I was doing at 5AM. So the next set of log entries reflect 1.3.10. I'm guessing this upgrade has something to do with why EPG123 1.3.10 hasn't worked since that 5AM manual work on 9/7.

Is there some way to "reset" and "clean house"? I don't want to lose my EPG123 configuration information, so if I have to "start over" I want to first preserve (or backup/export) my configuration data or folder/files so that I can easily restore/import it once whatever reinitialization, if necessary, is done. Please tell me exactly what I need to do to preserve my configuration and simplify recovery, if some extreme measures are required to clean house, start over, and resolve this SD-token error.

kkingsto

Posts: 15
Joined: Fri Oct 20, 2017 8:36 pm
Location:

HTPC Specs: Show details

#2

Post by kkingsto » Fri Sep 11, 2020 2:00 pm

Make sure you're not running both tasks at the same time.

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#3

Post by DSperber » Fri Sep 11, 2020 2:21 pm

kkingsto wrote:
Fri Sep 11, 2020 2:00 pm
Make sure you're not running both tasks at the same time.
What do you mean "both tasks"??? From the two different machines?? Of course not. I'm just trying to launch EPG123 on one machine, right this second, and it fails to start.

I'm going to try restoring the EPG123 program and associated data to the backup of 9/6, when I was still running successfully. If I can get back to normalcy with 1.3.5 I can take it forward from there, slowly. Maybe I shouldn't have just jumped from 1.3.5 to 1.3.10. I do have installers for intermediate versions 1.3.7 and 1.3.9, that I know I had used on my other "production" HTPC without issue eventually getting to 1.3.10. This "backup" HTPC obviously didn't see those step upgrades over the past 6 months or so since it's not really normally used, and I clearly wasn't paying attention until just a few days ago.

I will see if I can get things back to 1.3.5 as my first step.

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#4

Post by DSperber » Fri Sep 11, 2020 2:46 pm

Well, return to 1.3.5 was unsuccessful as far as getting the program to launch successfully. I actually took a more extreme approach and deleted all of the GaRyan2 and EPG123 folders completely, and then restored them from my 9/1 monthly FULL backups since it was just a few days older than 9/6. But it had no effect.

I've now UNINSTALLED EPG123, and deleted all relevant EPG123 and GaRyan2 folders. I then reinstalled 1.3.10 from stratch. And I was now able to launch EPG123.

I then entered my SD login credentials, and that worked as well. I'm going to now have to rebuild everything from scratch, but it's not a problem. This "backup" HTPC is really a duplicate of my other 'production" machine, and everything about tuners, channels, lineups, setups, is the same. Only difference is that I launch the nightly update at 1:40AM on my other machine and at 2:00AM on this machine, to keep them out of each other's way.

So I can simply duplicate all of the configuration items, including checking the "INCLUDE" channels on the two lineups, in maybe 20 minutes or so. And then I should be back in business.

Don't know what happened here but I suspect it was the big jump from 1.3.5 from 1.3.10.

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Fri Sep 11, 2020 3:11 pm

If you notice in your log file, the very first run of 1.3.10 ran perfectly fine. At most, updating from any version to the latest may require deleting your current scheduled task and creating another and I will note that on the website. Not being able to contact SD for the version check would point to something else but I have no idea what that would be. I would suspect AV/firewall software (Norton hates me), but that doesn't explain why the first run worked and the rest didn't.

So, first manual run worked fine.
Scheduled task run at 2AM kicked out while downloading schedules, started import (with garbage collection) and then ... nothing. I've never seen that. It should have jumped to importing the mxf file after the GC, but nothing.
After that, it was failing to contact SD.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#6

Post by DSperber » Fri Sep 11, 2020 3:17 pm

FOUND IT!

I was proceeding with the configuration of my newly reinstalled 1.3.10 EPG123. As I reported just above, I was actually able to launch EPG123 without a problem, in order to even begin configuring.

When I tried to create a new scheduled task I got a message about some kind of difference in the program location, one being C:\EPG123 and the other being C:\Program Files (x86)\EPG123. I then realized I must not have pointed the new reinstall to C:\EPG123 where the product had originally been installed on this machine back in 2017, and has remained there ever since throughout all upgrades through 1.3.5 and then even for 1.3.10 just a few days ago back on 9/7 when all of this SD Token error stuff started happening.

So, having realized I'd not forced the 1.3.10 install to go into C:\EPG123 like I really wanted (at least for consistency on this machine over the past three years, if not for any other reason) I again uninstalled EPG123, deleted all of the EPG123 and GaRyan2 folders all over the place, and reinstalled 1.3.10 one more time. And this time I was careful to change the target install folder to be my desired C:\EPG123.

And at completion of the install I checked the "launch EPG123" box in the final dialog page.

And, sure enough, once again the program now failed to launch... with that same "SD token" error message!!! I hadn't gotten that earlier, when I had overlooked changing the program target folder to C:\EPG123 and simply let it take the pre-populated default target of C:\Program Files (x86)\EPG123. That appears to be the key difference. When manually forcing C:\EPG123 it's not possible to launch the program. But when installing to C:\Program Files (x86)\EPG123 it launches fine.

I'm going to re-download the very latest 1.3.10 ZIP file (just to be sure I'm not missing something in the ZIP I am using). And I'm going to once again uninstall everything, including the related folders. And I'm going to reinstall one more time, to the default target location. That seems to be the trick to now successful launch of 1.3.10... you can no longer use C:\EPG123!!

Out of curiosity I double-checked my other machine, where EPG123 1.3.10 is currently working fine. And sure enough, I actually DO STILL HAVE C:\EPG123 on that partition. But it's years old, and its contents are obsolete. In fact I ALSO have C:\Program Files (x86)\EPG123, which in fact is the currently in-use program folder! Apparently I must have done an install sometime over the past few years on that machine and didn't notice the change of target location. So I clearly change the program folder and never realized the old location was no longer being used (and can obviously be deleted, which I should probably do... with caution, of course, given what I'm now aware of due to this current story).

So that's clearly why EPG123 1.3.10 is working fine on the other machine, because the program folder is C:\Program Files (x86)\EPG123. And that's clearly why EPG123 1.3.10 was failing on this machine, because the program folder was C:\EPG123.

I will correct this machine to be C:\Program Files (x86)\EPG123 because it really doesn't matter to me and looks better anyway. And if that solves the problem, then fine. I know Gary changed this whole install target stuff and where "data" goes many versions ago, but the original C:\EPG123 was "legacied" I though and should still have been usable. But apparently something new in 1.3.10 (or somewhere along the line from 1.3.5, since that WAS still working fine with C:\EPG123) had now made it mandatory to use C:\Program Files (x86)\EPG123.

This should be posted somewhere in FAQ or an installation note or the PDF instructions for install. The old C:\EPG123 acceptable target location is no longer usable.

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Fri Sep 11, 2020 3:21 pm

DSperber wrote:
Fri Sep 11, 2020 2:46 pm
So I can simply duplicate all of the configuration items, including checking the "INCLUDE" channels on the two lineups, in maybe 20 minutes or so. And then I should be back in business.
You could copy the c:\ProgramData\GaRyan2\epg123\epg123.cfg file from your other machine to this one and be ready to go. Just a note that is probably already too late.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#8

Post by garyan2 » Fri Sep 11, 2020 3:27 pm

DSperber wrote:
Fri Sep 11, 2020 3:17 pm
This should be posted somewhere in FAQ or an installation note or the PDF instructions for install. The old C:\EPG123 acceptable target location is no longer usable.
You can still install EPG123 anywhere and run it, it doesn't have to be in the program files area. Do you typically use the setup file, or do you use the portable zip file when installing/updating epg123? Using the setup file, it knows where the current install is and you won't even get prompted on where to install it... it uses the same location. So sounds like when you installed v1.3.10, that was the first time you used the setup file ... OR ... you uninstalled EPG123 before running setup and it is a whole new ball game at that point and you can install it anywhere.

If trying to install to c:\epg123, during setup make sure it doesn't change to c:\epg123\epg123. Not sure if that is what happened, or even the significance of that happening, just something to be aware of.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#9

Post by DSperber » Sat Sep 12, 2020 7:00 am

garyan2 wrote:
Fri Sep 11, 2020 3:27 pm
You can still install EPG123 anywhere and run it, it doesn't have to be in the program files area.
I believe it cannot be in C:\EPG123 any longer. That was what I actually did earlier today, and it failed to launch successfully. I had just uninstalled again, deleted all existing EPG123 and GaRyan2 folders everywhere, and then reinstalled specifcally setting the program target as C:\EPG123. And the very first launch of EPG123 produced the error message.

I then repeated the uninstall/delete preliminaries, and again reinstalled but this time let it go to the defaults C:\Program Files (x86)\EPG123. And sure enough, this time the very first launch started perfectly.

I was using 1.3.10.10 in both cases, so maybe that was the issue. Or, maybe it's just no longer possible in 1.3.10 to use C:\EPG123.

Finally getting back to this, as I've been away all day since this morning's last post. I've now taken your suggestion to simplify my life, having left things as they were this morning which was everything again uninstalled and deleted. So I first pre-created C:\ProgramData\GaRyan2\EPG123 and copied epg123.cfg from my other machine. I then ran the newly downloaded latest 1.3.10.20 installer, again letting it go to the default pre-populated target location of C:\Program Files (x86)\EPG123. And as expected, the program now launches perfectly once again. And furthermore, as you predicted everything in my configuration (from the other machine) was now duplicated on this machine. Zero effort. Perfect.

Do you typically use the setup file, or do you use the portable zip file when installing/updating epg123?
Only Setup, never portable.

Using the setup file, it knows where the current install is and you won't even get prompted on where to install it... it uses the same location So sounds like when you installed v1.3.10, that was the first time you used the setup file ... OR ... you uninstalled EPG123 before running setup and it is a whole new ball game at that point and you can install it anywhere.
Yes, the install of 1.3.10 recognized that the target location for the install should be exactly where it was before, namely C:\EPG123 as it has ALWAYS been on this machine... for three years. It didn't go to C:\Program Files (x86)\EPG123.

But that exposed what is the really the problem here, namely that 1.3.10 can no longer run from C:\EPG123 it would appear! Previously I had 1.3.5 running out of C:\EPG123 and it worked perfectly. It was simply the running of the 1.3.10 installer (with 1.3.5 currently installed) which went to the correct (i.e. the existing) target program folder of C:\EPG123, which exposed the apparent bug in 1.3.10 which makes it no longer possible to run the program from C:\EPG123.

I'm pretty sure I probably checked the "launch EPG123" at the completion of the 1.3.10 install, but didn't notice anything wrong in that very first post-upgrade launch. That was the run at 5AM on 9/7 which the log showed was successful. But it was subsequent launches (i.e. at 2AM on 9/8 and each night thereafter, as well as my manual attempts to launch it yesterday) which failed to start. And then again today I was able to replicate the launch failure with the total uninstall/reinstall to C:\EPG123.

That's certainly what it looks like based on my assorted results.

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Sat Sep 12, 2020 3:53 pm

I can certainly see why you suspect v1.3.10, but I am not seeing a problem here. I setup a VM and installed v1.3.5 in c:\epg123. Everything worked fine. I then ran the setup file for v1.3.10.20 to update epg123 and verified everything still runs fine. I get no errors, no issues communicating with Schedules Direct. I can't recreate what you are seeing.

I'm not sure what to look at here for you. Obviously if it only works for you in the Program Files folder, then just put it there and leave it be. I can verify EPG123 will still work in folders outside the Program Files folders.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

adam1991

Posts: 2871
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#11

Post by adam1991 » Sat Sep 12, 2020 4:44 pm

Permissions issue?

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#12

Post by DSperber » Sat Sep 12, 2020 5:17 pm

garyan2 wrote:
Sat Sep 12, 2020 3:53 pm
I can certainly see why you suspect v1.3.10, but I am not seeing a problem here. I setup a VM and installed v1.3.5 in c:\epg123. Everything worked fine. I then ran the setup file for v1.3.10.20 to update epg123 and verified everything still runs fine. I get no errors, no issues communicating with Schedules Direct. I can't recreate what you are seeing.

I'm not sure what to look at here for you. Obviously if it only works for you in the Program Files folder, then just put it there and leave it be. I can verify EPG123 will still work in folders outside the Program Files folders.
Strange.

Now that I see how quick and easy and simple it is to uninstall/reinstall and instantly have everything all pre-configured by simply pre-populating epg123.cfg in \ProgramData before running the installer, I will go back one more time and retry my earlier experiments. And of course I certainly had simply decided to let it go to the Program Files folder (i.e. default target location since you made that change a while back) since it makes absolutely no difference to me. The only reason it was ever in C:\EPG123 in the first place was because that's where you had initially placed it years ago, and that's where it still was back in March 2017 when I had built that machine. My other machine had been built in January 2019 and by that time you'd moved the default target, so that's why the second machine's program folder ended up there (since i obviously just ran the default install dialog as-is).

Anyway, I have two real Win7 physical machines I will retry this on, as well as having a WMC and EPG123 currently installed and available inside a VMWare Win7-VM guest running on a Win10 host. I will try the C:\EPG123 uninstall/reinstall in all three, to see if it really still fails for me or if I just needed more sleep. But the log doesn't lie, and my screenshots show what I got ever since upgrading from 1.3.5 to 1.3.10 on that machine with C:\EPG123 as the program folder... before I understood that this appeared to be the "trigger" to the symptom. And then yesterday's first conscious attempt to install there again and having it fail again, well I'm pretty convinced that's the story.

Might it be BitDefender? I think not.

I will report back on my repeat experiments.

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#13

Post by DSperber » Sat Sep 12, 2020 11:39 pm

Well, I give up. No explanation for the error, which I now determine to ONLY occur on this one Win7 machine.

I uninstalled/reinstalled on this machine one more time, and it failed again when targeted to C:\EPG123. I revise my problem description to state that it isn't the actual LAUNCH of the program itself which fails. That actually works, and the first launch contains blank SD username/password login credentials. But when I then enter my SD login credentials and push the LOGIN button, THAT is when the connection problem occurs complaining of "no response from SD for a token request".

I tried the same from-scratch first time install of EPG123 on Win10 (although of course I don't have WMC in Win10), again choosing C:\EPG123. And everything works perfectly.

I then looked into my Win7-VM setup Apparently I'd installed EPG123 go C:\EPG123 in Win7-VM. Furthermore, I had also apparently recently updated to 1.3.10 in Win7-VM, without incident or problem. Just to be double-sure I uninstalled/reinstalled selecting C:\EPG123 as the target. And still everything worked perfectly.

I also repeated the experiment on my second machine, i.e. my "production HTPC". And once again, installing to C:\EPG123 works perfectly.

So for some inexplicable reason this symptom only occurs on one particular Win7 machine. Although the two physical Win7 machines are very different (one is home-built ASUS motherboard Z170, and the other is a retail Lenovo M910t) they are otherwise essentially identical in terms of software and setup. And both have Ceton and Hauppauge tuners, and two SD channel lineups into EPG123. Both use BitDefender. Both have all partitions "shared" with full-access, so that all partitions on both machines are available on either machine.

Can't explain it. But I'm willing to let it go. I've now uninstalled/reinstalled ALL THREE of my Win7 environments, choosing C:\Program Files (x86)\EPG123 as the target for all three. And it works perfectly on all three systems, including the machine which fails when using C:\EPG123. I have absolutely no problem using this Program Files location which simply works problem-free universally.

No explanation. I give up. Perhaps if I knew what the "SD token request" function was, how it worked, what it depended on, etc., maybe we might have a clue as to why it is failing on this one particular machine if the program is coming from C:\EPG123.

Otherwise, I'll just put this in the category of that very rare issue where "I have NOT emerged victorious".

User avatar
garyan2

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

HTPC Specs: Show details

#14

Post by garyan2 » Sat Sep 12, 2020 11:53 pm

Just to answer your question that may lead to an answer. From your log entries above...

Code: Select all

[9/11/2020 4:33:25 AM] ===============================================================================
[9/11/2020 4:33:25 AM]  Activating the epg123 configuration GUI. version 1.3.10.0
[9/11/2020 4:33:25 AM] ===============================================================================
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:26 AM] [ERROR] Did not receive a response from Schedules Direct for a version check.
[9/11/2020 4:33:26 AM] [ INFO] SD API WebException Thrown. Message: Unable to connect to the remote server , Status: ConnectFailure
[9/11/2020 4:33:26 AM] [ERROR] Failed to complete request. Exiting
[9/11/2020 4:33:26 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
When the configuration GUI opens, the first thing it does is reach out to Schedules Direct to find out what the latest version of EPG123 is (Did not receive a response from Schedules Direct for a version check). The second thing it does is try to login in to get a token for the session so it can download your lineups and populate the right side of the GUI (Did not receive a response from Schedules Direct for a token request). Both are failing to contact SD which is why I initially thought of the firewall or AV software. But being able to run in Program Files and not the epg123 folder makes me think the firewall is more likely.

Hopefully this may lead to an answer or a strong theory.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#15

Post by DSperber » Sun Sep 13, 2020 12:10 am

Interesting. I mentioned BitDefender, but it's installed on both machines (and also in Win10) so it wouldn't seem to be worthy of considering.

I will retry this one more time right now on the failing machine, this time disabling BitDefender firewall. I certainly have had issues relating to BitDefender firewall in the past, but there's no difference in BitDefender firewall configuration on any of these machines. Pretty much standard default.

Nevertheless... I will report back shortly.

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#16

Post by DSperber » Sun Sep 13, 2020 1:12 am

Well, THAT WAS IT! When I disabled BitDefender Firewall on Z170 (the failing Win7 machine) sure enough the SD connection was allowed, and the LOGIN completed normally, even when the program was installed to C:\EPG123. It was with Firewall enabled that the program would fail when coming from C:\EPG123 and would work when coming from C:\Program Files (x86)\EPG123.

Looking closer, it turns out BitDefender's Firewall on Z170 WAS actually configured differently on the two machines, Z170 vs. DFW (the working Win7 machine). I don't know why this should have been (my speculations arediscussed later), but there's no question the failing Z170 machine had "disallow" enabled for C:\EPG123\epg123.exe whereas it had "allow" for C:\Program Files (x86)\EPG123\epg123.exe. There were two entries defined because there actually were two different locations for the program during the history of the installs.

Image

In contrast, the BitDefender firewall configuration also showed two firewall entries corresponding to EPG123.EXE from the two different program folders. However BOTH of them were set to "allow".

Image

So, all I had to do was "allow" the C:\EPG123 entry and now, sure enough, connection to SD worked perfectly.

Image


Ok. Case closed. Now, how did this unexpected difference in my two machines occur?? Here's my theory.

The first time a program tries to do something or access a "resource" BitDefender Firewall is "protecting", a popup is presented allowing setting access to that protected resource or allowing that function (i.e. "allow"), or to continue the protection and blockage (i.e. "continue protecting") which denies the operation.

Now remember that Z170 was built back in early 2017, at which time I was not using BitDefender as my anti-virus/firewall. I was still using Microsoft Security Essentials (MSE). I didn't actually install BitDefender until around March 2019. But I was using EPG123 for a long time now, certainly back in 2017 when Z170 was built. And the target program folder for EPG123 was defaulted to C:\EPG123 back then, so that's where the program resided when BitDefender was installed in March 2019.

And C:\EPG123\epg123.exe has apparently been running without any interference from BitDefender starting from March 2019 until right up to Wednesday of this week in September 2020, when I happened to upgrade from 1.3.5 to 1.3.10. I am speculating that you made some program change between 1.3.5 and 1.3.10 which involved this "SD connection token" or related functionality. It must not have been implemented the same way in 1.3.5 as it is now in 1.3.10, because otherwise I would have seen the same firewall-caused problem with 1.3.5 and I did not.

What's odd is that normally the first time BitDefender sees this "protected request" it should have popped up the action dialog for me to respond to. I certainly never saw such a popup when I upgraded from 1.3.5 to 1.3.10 on Wednesday, as I would have imagined I should have. I only began experiencing the "block" result, as if I'd responded to continue protection for this C:\EPG123\epg123.exe program. But I was never presented with this expected dialog. Maybe it just took this "block" decision for some other unknown reason.

Anyway, there's no question that this is the history on Z170, where EPG123 has always been installed to C:\EPG123. So C:EPG123\epg123.exe was already installed when BitDefender was later installed in 2019, simultaneous with my decision to use BitDefender on my newly acquired M910t.

In contrast, when M910t was built in 2019, I installed BitDefender right away. I never used MSE on that machine. And then EPG123 was installed as part of the WMC installation, but the target program folder location was by now the new default C:\Program Files (x86)\EPG123. Again, I don't actually remember if I ever received any popup dialog from BitDefender the first time I ran EPG123 since it was quite a while ago, but I suspect not. I suspect something about what a newly installed EPG123 is doing is resulting in an automatic response of "allow". I say this because just a little while ago when I was experimenting for this thread and installed to C:\EPG123 on M910t, somehow C:\EPG123\epg123.exe was automatically "allow". I absolutely did not see any popup from BitDefender, so this "allow" was obviously automatic. And that's how BOTH locations are "allow" on M910t, given the history of BitDefender on that machine.

So, in summary, Z170 had EPG123 installed (to C:\EPG123) before BitDefender was installed two years later. For M910t BitDefender was present from day 1 in early 2019, and EPG123 was installed during the next few days. BitDefender was installed on Z170 (replacing MSE) when I decided to use the product first on M910t, and then on all my other machines.


Bottom line: BitDefender on M910t just a while ago, when I installed EPG123 to C:\EPG123 for the experiment (with BitDefender already installed), automatically set the "allow". This obviously then allowed EPG123.EXE to start properly and connect to SD. In contrast, on Z170 EPG123 was initially installed (t C:\EPG123) years before BitDefender was installed. And as a consequence (for some reason) executing previously installed EPG123.EXE even though BitDefender was now installed did NOT AUTOMATICALLY ALLOW program execution... which was NOT CRITICAL up through version 1.3.5 of EPG123.

So something changed after 1.3.5 and which is now present in 1.3.10, dealing with this intitial SD connection at LOGIN, and which now is "blocked" by BitDefender unless its Firewall entry is change to "allow". I assume you will know what you changed here since 1.3.5, which would now be under the watchful eye of BitDefender when using 1.3.10 but which was of no concern back with 1.3.5.

adam1991

Posts: 2871
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#17

Post by adam1991 » Sun Sep 13, 2020 11:12 am

so, like I said: permissions issue.

DSperber

Posts: 279
Joined: Thu Jan 16, 2014 1:35 am
Location: Marina Del Rey, CA

HTPC Specs: Show details

#18

Post by DSperber » Sun Sep 13, 2020 1:05 pm

adam1991 wrote:
Sun Sep 13, 2020 11:12 am
so, like I said: permissions issue.
I obviously didn't understand what you were referring to here. Had you added something additional, like "check your firewall", then I would have understood the "permissions" reference.

Anyway, that does turn out to have been the answer. So thank you for the poke... even if I didn't realize what you were saying.

But again, the interesting thing is that whatever EPG123 is now doing in 1.3.10, apparently it is causing BitDefender to "auto-allow" the EPG123.EXE program (whatever folder it is installed into) to run without issue. So during yesterday's first-time-ever installs into both folders as part of the experimenting for this thread, the install into C:\Program Files x(86)\EPG123 on Z170 automatcally was "allowed" and I could start the program and LOGIN without issue. I was never prompted for any decision to allow or block by BitDefender. It was just auto-allowed. And EPG123.EXE running from here is allowed and not blocked.

It was only the much earlier install of EPG123 to C:\EPG123 back in 2017 when MSE was still operating on the machine, before installing BitDefender to replace MSE, that was the instance which this week resulted in my problem when doing the upgrade of EPG123 from 1.3.5 to 1.3.10. Since apparently the C:\EPG123\epg123.exe program had never before gotten auto-allowed, the seemingly different connection logic now present in 1.3.10 (which now with 1.3.10 is seemingly doing something that "concerns" BitDefender Firewall whereas with 1.3.5 it did not), the fact that it was still set to "block" instead of "allow" is what was responsible for the problem reported in this thread.

As far as my other machine M910t goes, when I installed EPG123 first-time-ever into C:\EPG123 on M910t yesterday, well that brand new item also appears to have gotten auto-allowed. Again, it launched, did its LOGIN, and had no problem. Whatever is new in 1.3.10 (vs. 1.3.5) regarding this SD connection, apparently it now is of "concern" to BitDefender but getting auto-allowed so that is permitted and EPG123 completes the LOGIN without issue.

As far the second (older) Firewall item of C:\Program Files (x86)\EPG123\epg123.exe on M910t, that one obviously was born during the several days of software/customization build-out of my new M910t machine back in early 2019. Chronologically, I had already installed BitDefender early on when then a few days later I installed EPG123 into C:\Program Files (x86)\EPG123 and ran EPG123.EXE for the first time. That aparently got auto-allowed and has been running that way ever since. It seems that whatever change occurred between 1.3.5 and 1.3.10 was not an issue on M910t, because the installed and running EPG123.EXE had long ago been auto-allowed by BitDefender.


So each machine had TWO program items in the BitDefender Firewall list. For M910t, both items had been "born" AFTER BitDefender itself was installed and operational on the machine. EPG123 was installed AFTER BitDefender. One had been "born" back in in early 2019 when the machine was built, and the second was "born" just yesterday as part of my experimenting. But it's clear BOTH of the program items were marked as "allow", explaining why either target location for EPG123 runs quietly and successfully on M910t.

And in contrast, while Z170 also now had TWO program items in the BitDefender Firewall list, only one of them was marked as "allow". This was the item created just yesterday for C:\Program Files (x86)\EPG123\epg123.exe as part of my experimenting and try of installing EPG123 to that location. And obviously it got auto-allowed from that location yesterday. However the much older (three years older) entry for C:\EPG123\epg123.exe which was created back in 2017 when I built Z170 (and was still using MSE at the time, not BitDefender), apparently the subsequent use of EPG123.EXE after converting to BitDefender NEVER GOT AUTO-ALLOWED!!! It was actually still marked as "block" but somehow didn't trigger any problem running for the past two years of operating under BitDefender, right up through version 1.3.5 of EPG123.

It was only the other day, when EPG123 was upgraded from 1.3.5 to 1.3.10 on Z170, that what must be something "new" in EPG123's SD connection post-1.3.5 which has now become "of concern" to BitDefender. And the "block" status apparently is what now suddenly (just this week, after upgrading from 1.3.5 to 1.3.10) triggered the SD connection error situation on Z170.

And whatever would normally have caused BitDefender to auto-allow EPG123.EXE for a newly (i.e. truly first-time) installed EPG123, that didn't happen when I repeatedly uninstalled/reinstalled EPG123 into the C:\EPG123 location. BitDefender was still using its original program item from three years ago. Had I realized this before now, I simply could have manually ALLOWED that program item (as I've now done, to prove that was the problem all along). Alternatively, I could have DELETED the very old item (which was showing as BLOCK when I discovered it). Then when I reinstalled EPG123 into C:\EPG123 again as part of this experimenting, it would have been "FIRST TIME" and no doubt would get auto-allowed by BitDefender as happened in all of my other first-time tests yesterday on other machine (and including in Win10).


Nevertheless, the mystery is now solved. It absolutely WAS my BitDefender Firewall which was the cause of the problem but just on Z170. And EPG123.EXE 1.3.10 (or at least post 1.3.5), no matter where it is installed to, MUST BE "ALLOWED" in the Firewall list in order for it to now work properly. That "allow" can either be from auto-allow as seems to occur now for any new install of EPG123 1.3.10 on any machine already running BitDefender, or manual ALLOW if that is necessary for an old install of EPG123 before BitDefender got installed on the same machine.

One way or another, EPG123.EXE 1.3.10 must now be "allowed" by the Firewall. It clearly was not necessary with 1.3.5, but it is now with 1.3.10.

adam1991

Posts: 2871
Joined: Sat Jun 11, 2011 2:31 pm
Location:

HTPC Specs: Show details

#19

Post by adam1991 » Sun Sep 13, 2020 11:24 pm

well, there's absolutely no way I could have known nearly enough about your system to tell you WHAT would cause permissions issue.

But it was absolutely clear to me that you had a permissions issue. No question. It was up to you to poke around and discover what might be interfering with permissions on the folder in question.

And in fact, I never would have guessed that you had BitDefender. I might have said "check your antivirus program," but even that was beyond the scope of what I was suggesting. I simply said it was a permissions issue, and absent more info had to leave it at that.

User avatar
IT Troll

Posts: 801
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#20

Post by IT Troll » Mon Sep 14, 2020 7:09 am

When hitting it issues like this it is always the firewall. Except when it is the certificate. :)
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1.1

Post Reply