2020 - The year in [ERROR]s

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
User avatar
StinkyImp

Posts: 386
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

2020 - The year in [ERROR]s

#1

Post by StinkyImp » Sat Jan 02, 2021 5:26 pm

Seems like most of my errors involved contact with Schedules Direct. The bonus side of these errors is it helped me track down a "flaky" component in my wifi setup! :D

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.6 (64 bit)
Report Created on 01/02/2021 at 10:03:27
================================================================
[3/12/2020 12:15:32 AM] [ERROR] Failed to complete request. Exiting
[3/12/2020 12:15:32 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/12/2020 12:15:32 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[3/12/2020 2:04:32 AM] [ERROR] The MXF file imported is 25.75 hours old.
[4/13/2020 12:15:09 AM] [ERROR] Failed to complete request. Exiting
[4/13/2020 12:15:09 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[4/13/2020 12:15:09 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[4/13/2020 12:15:47 AM] [ERROR] The MXF file imported is 24.01 hours old.
[4/15/2020 12:15:32 AM] [ERROR] Failed to complete request. Exiting
[4/15/2020 12:15:32 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[4/15/2020 12:15:32 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[4/15/2020 12:16:09 AM] [ERROR] The MXF file imported is 24.01 hours old.
[4/19/2020 12:15:08 AM] [ERROR] Failed token request. code: 3000 , message: Server offline for maintenance. , datetime: 2020-04-19T07:15:47Z
[4/19/2020 12:15:09 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Failed token request. code: 3000 , message: Server offline for maintenance. , datetime: 2020-04-19T07:15:47Z
[4/19/2020 12:15:47 AM] [ERROR] The MXF file imported is 24.01 hours old.
[4/20/2020 12:15:08 AM] [ERROR] Failed token request. code: 3000 , message: Server offline for maintenance. , datetime: 2020-04-20T07:15:47Z
[4/20/2020 12:15:08 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Failed token request. code: 3000 , message: Server offline for maintenance. , datetime: 2020-04-20T07:15:47Z
[4/20/2020 12:15:47 AM] [ERROR] The MXF file imported is 48.01 hours old.
[4/22/2020 12:15:16 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[4/22/2020 12:15:16 AM] [ERROR] Did not receive a response from Schedules Direct for  98 station's daily schedules. (0:00:00:00.4970284)
[4/22/2020 12:15:16 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[4/22/2020 12:15:16 AM] [ERROR] Failed to create MXF file. Exiting.
[6/6/2020 12:15:13 AM] [ERROR] Failed to complete request. Exiting
[6/6/2020 12:15:13 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 100 station's daily schedules. (0:00:00:00.9410538)
[6/6/2020 12:15:13 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[6/6/2020 12:15:13 AM] [ERROR] Failed to create MXF file. Exiting.
[6/6/2020 12:15:51 AM] [ERROR] The MXF file imported is 24.00 hours old.
[6/15/2020 12:15:05 AM] [ERROR] Failed to complete request. Exiting
[6/15/2020 12:15:05 AM] [ERROR] Did not receive a response from Schedules Direct for Md5s of 100 station's daily schedules. (0:00:00:00.5710326)
[6/15/2020 12:15:05 AM] [ERROR] Problem occurred during getMd5ScheduleEntries(). Exiting.
[6/15/2020 12:15:05 AM] [ERROR] Failed to create MXF file. Exiting.
[6/15/2020 12:15:43 AM] [ERROR] The MXF file imported is 24.01 hours old.
[6/27/2020 12:15:11 AM] [ERROR] Failed to complete request. Exiting
[6/27/2020 12:15:11 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[6/27/2020 12:15:11 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[6/27/2020 12:26:59 AM] [ERROR] The MXF file imported is 24.19 hours old.
[7/11/2020 12:15:18 AM] [ERROR] Failed to complete request. Exiting
[7/11/2020 12:15:18 AM] [ERROR] Did not receive a response from Schedules Direct for  18 generic program descriptions. (0:00:00:00.4220241)
[7/11/2020 12:15:19 AM] [ERROR] Unhandled exception caught from epg123.exe. message: The given key was not present in the dictionary.
[7/11/2020 12:15:50 AM] [ERROR] The MXF file imported is 24.01 hours old.
[8/2/2020 12:15:20 AM] [ERROR] Failed to complete request. Exiting
[8/2/2020 12:15:20 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[8/2/2020 12:15:20 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[8/2/2020 12:22:58 AM] [ERROR] The MXF file imported is 48.13 hours old.
[9/16/2020 12:15:11 AM] [ERROR] Failed to complete request. Exiting
[9/16/2020 12:15:11 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[9/16/2020 12:15:11 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[9/16/2020 12:24:21 AM] [ERROR] The MXF file imported is 31.15 hours old.
[11/6/2020 12:15:13 AM] [ERROR] Failed to complete request. Exiting
[11/6/2020 12:15:13 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[11/6/2020 12:15:13 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[11/6/2020 12:15:44 AM] [ERROR] The MXF file imported is 24.01 hours old.

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log and trace_2020.log
Search String:		[ERROR]
Date Range:		01/01/2020 thru 12/31/2020 (366 days)
Total results found:	52
Query time:		14 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	1/1/2020 thru 1/2/2021 (368 days)
Total lines processed:	26552

===== SYSTEM INFORMATION =======================================
Operating System:	Windows 7 Professional (64 bit)
Processor:		Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Total RAM:		8.00 GB
ehshell version:	6.1.7601.23434
EPG123 version:		1.6.0.6
Last boot time:		December 09, 2020 - 05:37 AM
System Uptime:		24 Days 04 Hours 25 Minutes

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Sun Jan 03, 2021 5:52 pm

Awesome. :thumbup:
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
rmeden

Posts: 67
Joined: Wed Jul 29, 2015 3:39 pm
Location: Schedules Direct

HTPC Specs: Show details

#3

Post by rmeden » Sun Jan 03, 2021 9:45 pm

part of the problem is "Did not receive a response from Schedules Direct for a token request." isn't an actionable message. *WHY* were you not able to get a token? I get about 5 questiosns a week about this at SD. All I can say is their account is fine and send them here.

"did not receive a response" to most folks could mean anything. Maybe add the OS error from the TCP Open call?
  • Were you unable to get an IP? ( better message: DNS failing to get an IP for Schedules Direct)
  • Did the connection fail? ( better message: Unable to connect to schedules direct )
  • Did a connection occur (two way tunnel established) and SD-JSON not respond ( better message: No response to token request from Schedules Direct)
  • Did SD respond with a status message? (expired, outage in progress, bad password)
Reporting a actionable error message will make diagnosis faster, and probably reduce posts here and emails to SD (where I just send them here)

Robert

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Sun Jan 03, 2021 10:22 pm

The filter StinkyImp posted is just the [ERROR] entries, there will be more information in the log file such as:

Code: Select all

[12/6/2019 4:22:04 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.

[1/3/2020 4:22:02 AM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2020-01-03T11:22:02Z

[3/11/2020 4:22:19 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError

[4/19/2020 4:22:01 AM] [ERROR] Failed token request. code: 3000 , message: Server offline for maintenance. , datetime: 2020-04-19T11:22:01Z

[4/20/2020 4:27:51 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.

[5/15/2020 7:16:04 AM] [ INFO] SD responded with error code: 4003 , message: Invalid username or token has expired. , serverID: 20141201.web.3 , datetime: 2020-05-15T14:16:04Z

[9/21/2020 9:59:06 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (503) Server Unavailable. , Status: ProtocolError
As you can see, if I make connection with SD and it returns an error code, it gets logged. If a connection is made but is prematurely closed, it get logged. If a connection fails, the web exception is logged with the error code. DNS errors will also be logged. Since I do retries on requests, I didn't want to set the status to [ERROR] until all retries failed so it falls into the "did not receive a response" message.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
StinkyImp

Posts: 386
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

#5

Post by StinkyImp » Mon Jan 04, 2021 4:00 pm

rmeden wrote:
Sun Jan 03, 2021 9:45 pm
Reporting a actionable error message will make diagnosis faster, and probably reduce posts here and emails to SD (where I just send them here)

Robert
This is one of those cases where my words didn't accurately reflect the operation of my thoughts. The post was intended to be purely positive.

For EPG123 -> I meant to imply that it ran (on the whole) flawlessly for the entire year (and I updated to every new version Gary posted).

For Schedules Direct -> I didn't report a single error because they were mostly on my end. It helped me track down a flaky erratic wifi component, DNS issues with my VPN or internet provider and in one case with my router. There was no reportable fault with your service. The positive side was it helped me to seek out and repair weaknesses in my own setup!

I guess I should have said in all sincerity... Great job guys! Thank you for providing me with these wonderful programs and services! You're the best! :D :clap: :thumbup: :wave:

User avatar
rmeden

Posts: 67
Joined: Wed Jul 29, 2015 3:39 pm
Location: Schedules Direct

HTPC Specs: Show details

#6

Post by rmeden » Tue Jan 05, 2021 9:05 pm

garyan2 wrote:
Sun Jan 03, 2021 10:22 pm
As you can see, if I make connection with SD and it returns an error code, it gets logged. If a connection is made but is prematurely closed, it get logged. If a connection fails, the web exception is logged with the error code. DNS errors will also be logged. Since I do retries on requests, I didn't want to set the status to [ERROR] until all retries failed so it falls into the "did not receive a response" message.
Good to know detailed logging is there. When I get a question @ SD, they only say "unable to get a token.. please fix it" :) I'll keep sending them here :)

Robert

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Tue Jan 05, 2021 10:01 pm

rmeden wrote:
Tue Jan 05, 2021 9:05 pm
" :) I'll keep sending them here :)
...and I'll keep asking them to look at the log file. Most of the times for failing to get a token, that I've seen, is due to the user renewing their membership, changing their password because they forgot what it was, and not updating the password in epg123.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
rmeden

Posts: 67
Joined: Wed Jul 29, 2015 3:39 pm
Location: Schedules Direct

HTPC Specs: Show details

#8

Post by rmeden » Tue Jan 05, 2021 10:46 pm

garyan2 wrote:
Tue Jan 05, 2021 10:01 pm
the user renewing their membership, changing their password because they forgot what it was, and not updating the password in epg123.
sooooo many of those!!!! I log password resets for that very reason. First thing I check in the logs. They usually report their payment hasn't taken effect.

Sometimes I have fun with them... "do you remember what you right before renewing????"

I should make a note on the password reset pages to be sure to update their applications... oh wait, *I DO* :)

Ahhhh joys of customer support.

Robert

Post Reply