Error When Running EPG123

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
choliscott

Posts: 598
Joined: Mon Dec 19, 2011 8:56 am
Location:

HTPC Specs: Show details

Error When Running EPG123

#1

Post by choliscott » Sun Jul 10, 2016 9:48 am

I decided to update my HTPC for the free W10 upgrade before it the end of the month & restored W7 from a system image.

When I went to run EPG123, it crashes after about a minute, with the following error:

[7/10/2016 2:25:25 AM] ===============================================================================
[7/10/2016 2:25:25 AM] Activating the epg123 configuration GUI.
[7/10/2016 2:25:25 AM] ===============================================================================
[7/10/2016 2:25:26 AM] [ INFO] epg123 is up to date. version: 0.9.9
[7/10/2016 2:25:28 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/10/2016 2:25:29 AM] [ INFO] Status request successful. account expires: 2016-09-06T03:30:05Z , lineups: 1/4 , lastDataUpdate: 2016-07-09T23:51:54Z
[7/10/2016 2:25:29 AM] [ INFO] system status: Online , message: No known issues.
[7/10/2016 2:25:29 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/10/2016 2:25:29 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-WA46459-X.
[7/10/2016 2:25:30 AM] [ INFO] Successfully queried the Task Scheduler for status. status: Ready. Last Run 7/10/2016 2:22:39 AM; Exit: 0xE0434352
[7/10/2016 2:25:32 AM] ===============================================================================
[7/10/2016 2:25:32 AM] Beginning epg123 update execution.
[7/10/2016 2:25:32 AM] ===============================================================================
[7/10/2016 2:25:32 AM] [ INFO] epg123 version 0.9.9 , DaysToDownload: 14 , PrefixEpisodeTitle: False , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[7/10/2016 2:25:32 AM] [ INFO] Successfully retrieved TMDb configurations.
[7/10/2016 2:25:33 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/10/2016 2:25:33 AM] [ INFO] epg123 is up to date. version: 0.9.9
[7/10/2016 2:25:33 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/10/2016 2:25:33 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-WA46459-X.
[7/10/2016 2:25:34 AM] Entering getAllScheduleEntryMd5s() for 14 days on 230 stations.
[7/10/2016 2:25:34 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[7/10/2016 2:25:34 AM] [ERROR] SD responded with error code: 4003 , message: Invalid username or token has expired. , serverID: 20141201.web.2 , datetime: 2016-07-10T09:25:34Z
[7/10/2016 2:25:34 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 230 station's daily schedules.
[7/10/2016 2:25:34 AM] [ERROR] Unhandled exception caught from main program. message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

choliscott

Posts: 598
Joined: Mon Dec 19, 2011 8:56 am
Location:

HTPC Specs: Show details

#2

Post by choliscott » Sun Jul 10, 2016 9:49 am

Ok I tried about 15 minutes later & it seemed to work as normal

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Sun Jul 10, 2016 5:14 pm

Typically only see something like this when you have 2 instances of epg123 running. Only a single token can exist at a time so if you open an instance of epg123 while another session is running, the new session invalidates the last token and creates a new one. It is also possible there was a Schedules Direct server issue.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply