Epg123 Unhandled Exception

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
rimmel

Posts: 86
Joined: Tue Aug 27, 2013 10:36 pm
Location:

HTPC Specs: Show details

Epg123 Unhandled Exception

#1

Post by rimmel » Sun Oct 30, 2016 12:51 am

I just attempted to run Epg123 and it crashed after only a few display lines in the command window. I was able to collect the following information:


Application Event Log Entry


Application: epg123.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Newtonsoft.Json.JsonReaderException
Stack:
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(Newtonsoft.Json.JsonReader, System.Type, Boolean)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(Newtonsoft.Json.JsonReader, System.Type)
at Newtonsoft.Json.JsonConvert.DeserializeObject(System.String, System.Type, Newtonsoft.Json.JsonSerializerSettings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String, Newtonsoft.Json.JsonSerializerSettings)
at epg123.sdApi.SdApi.sdGetRequestResponse(METHODS, System.String, System.Object, Boolean)
at epg123.sdApi.SdApi.sdGetScheduleMd5s(epg123.sdApi.sdScheduleRequest[])
at epg123.sdJson2mxf.getMd5ScheduleEntries(System.String[], Int32)
at epg123.sdJson2mxf.getAllScheduleEntryMd5s(Int32) at epg123.sdJson2mxf..ctor(epg123.epgConfig)
at epg123.Program.Main(System.String[])

Epg123 Trace Log Entries

Code: Select all

[10/29/2016 5:14:41 PM] ===============================================================================
[10/29/2016 5:14:41 PM]  Activating the epg123 configuration GUI.
[10/29/2016 5:14:41 PM] ===============================================================================
[10/29/2016 5:14:42 PM] [ INFO] epg123 is up to date. version: 1.0.2
[10/29/2016 5:14:45 PM] [ INFO] Token request successful. serverID: 20141201.web.2
[10/29/2016 5:14:45 PM] [ INFO] Status request successful. account expires: 2017-01-20T01:58:13Z , lineups: 1/4 , lastDataUpdate: 2016-10-29T14:32:09Z
[10/29/2016 5:14:45 PM] [ INFO] system status: Online , message: No known issues.
[10/29/2016 5:14:45 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[10/29/2016 5:14:46 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-WA46544-X.
[10/29/2016 5:14:46 PM] [ INFO] Did not find the daily update task in the Task Scheduler. status: No task is scheduled to run.
[10/29/2016 5:14:53 PM] ===============================================================================
[10/29/2016 5:14:53 PM]  Beginning epg123 update execution.
[10/29/2016 5:14:53 PM] ===============================================================================
[10/29/2016 5:14:53 PM] [ INFO] epg123 version 1.0.2 , DaysToDownload: 21 , PrefixEpisodeTitle: False , AppendEpisodeDesc: True , AutoImport: True , TMDbCoverArt: True , LogoOverride: False , Automatch: True , AutoAddNew: True
[10/29/2016 5:14:53 PM] [ INFO] Successfully retrieved TMDb configurations.
[10/29/2016 5:14:54 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[10/29/2016 5:14:54 PM] [ INFO] epg123 is up to date. version: 1.0.2
[10/29/2016 5:14:54 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[10/29/2016 5:14:54 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-WA46544-X.
[10/29/2016 5:14:55 PM] Entering getAllScheduleEntryMd5s() for 21 days on 491 stations.
If I can collect any more information regarding this problem, just let me know.

rimmel

Posts: 86
Joined: Tue Aug 27, 2013 10:36 pm
Location:

HTPC Specs: Show details

#2

Post by rimmel » Sun Oct 30, 2016 1:28 am

I waited about an hour and reran Epg123 and it worked OK. No idea what happened before?

As a side note. When this exception happened more error information was displayed in the command window, but none of this stuff appeared in the trace log. I was not able to cut and paste command window messages because the entire command window greyed out right after the messages appeared. Maybe a way could be discovered to direct all command window messages (especially error messages) into the trace log.

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Sun Oct 30, 2016 2:42 am

rimmel wrote:I waited about an hour and reran Epg123 and it worked OK. No idea what happened before?

As a side note. When this exception happened more error information was displayed in the command window, but none of this stuff appeared in the trace log. I was not able to cut and paste command window messages because the entire command window greyed out right after the messages appeared. Maybe a way could be discovered to direct all command window messages (especially error messages) into the trace log.
I'm thinking you had an I/O error as well which failed to write to the trace log file. Everything written to the Event Log should have been written to the trace file as well. There is also a final catch in the program to log any error that gets through the main program.

Not sure what caused the original error, but looks like it didn't like a return message from Schedules Direct... could have been malformed. Since it ran fine the second time, it wasn't anything that was cached.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply