Recurring SD API WebException

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: 401
Joined: Thu May 11, 2017 7:53 pm
Location:

HTPC Specs: Show details

Recurring SD API WebException

#1

Post by StinkyImp » Thu Mar 18, 2021 2:04 pm

Over the years my solution for this was to simply ignore it. This error has always resolved itself within a day or two. This is first time I've ever received it for three days straight.

I can login to SD with my credentials so I know I'm at least able to reach their website and verify that my login information is valid. I looked at their forums and didn't see anyone else reporting this issue recently.

I'm pretty sure this isn't an EPG123 problem because it worked fine on the first day of my update. It has only failed for the three subsequent days.

Code: Select all

Schedules Direct account
Country: 	United States
Status: 	Active
Expires: 	Saturday, February 12, 2022

EPG123 VERSION HISTORY:
[3/13/2021 12:15:19 AM]  Beginning epg123 client execution. version 1.6.2.9
[3/14/2021 12:16:33 AM]  Beginning epg123 client execution. version 1.6.2.9
[3/15/2021 12:15:23 AM]  Beginning epg123 client execution. version 1.6.3.0
[3/16/2021 12:15:21 AM]  Beginning epg123 client execution. version 1.6.3.0
[3/17/2021 12:15:12 AM]  Beginning epg123 client execution. version 1.6.3.0
[3/18/2021 12:15:11 AM]  Beginning epg123 client execution. version 1.6.3.0

LOG DATA:
[3/15/2021 12:15:07 AM] ===============================================================================
[3/15/2021 12:15:07 AM]  Beginning epg123 update execution. version 1.6.3.0
[3/15/2021 12:15:07 AM] ===============================================================================
[3/15/2021 12:15:08 AM] [ INFO] Beginning EPG123 update execution. 2021-03-15 07:15:08Z
[3/15/2021 12:15:08 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : True , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: False , OADOverride : True , TMDbCoverArt: True , IncludeSDLogos : True , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[3/15/2021 12:15:09 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[3/15/2021 12:15:09 AM] [ INFO] Status request successful. account expires: 2022-02-12T14:47:08Z , lineups: 1/4 , lastDataUpdate: 2021-03-15T05:14:25Z
[3/15/2021 12:15:09 AM] [ INFO] system status: Online , message: No known issues.
[3/15/2021 12:15:10 AM] [ INFO] Successfully retrieved TMDb configurations.
[3/15/2021 12:15:11 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.

[3/16/2021 12:15:20 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/16/2021 12:15:20 AM] [ERROR] Failed to complete request. Exiting
[3/16/2021 12:15:20 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/16/2021 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.
[3/16/2021 12:15:20 AM] [ERROR] Failed to create MXF file. Exiting.
[3/16/2021 12:15:48 AM] [ERROR] The MXF file imported is 24.01 hours old.

[3/17/2021 12:15:11 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/17/2021 12:15:11 AM] [ERROR] Failed to complete request. Exiting
[3/17/2021 12:15:11 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/17/2021 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.
[3/17/2021 12:15:12 AM] [ERROR] Failed to create MXF file. Exiting.
[3/17/2021 12:15:39 AM] [ERROR] The MXF file imported is 48.01 hours old.

[3/18/2021 12:15:11 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (502) Bad Gateway. , Status: ProtocolError
[3/18/2021 12:15:11 AM] [ERROR] Failed to complete request. Exiting
[3/18/2021 12:15:11 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/18/2021 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.
[3/18/2021 12:15:11 AM] [ERROR] Failed to create MXF file. Exiting.
[3/18/2021 12:15:38 AM] [ERROR] The MXF file imported is 72.01 hours old.
Has anyone else experienced this recently?

Any direction on where to look for solutions?

User avatar
d00zah

Posts: 160
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#2

Post by d00zah » Thu Mar 18, 2021 2:46 pm

Looked like a transient SD issue?

Code: Select all

[3/16/2021 3:30:03 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/16/2021 3:30:03 AM] [ERROR] Failed to complete request. Exiting
[3/16/2021 3:30:03 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/16/2021 3:30:03 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[3/16/2021 3:30:03 AM] [ERROR] Failed to create MXF file. Exiting.
[3/16/2021 3:30:03 AM] [ INFO] epg123 update execution time was 00:00:03.4323432.
Fine on the 17th.

Code: Select all

[3/18/2021 3:30:05 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/18/2021 3:30:05 AM] [ERROR] Failed to complete request. Exiting
[3/18/2021 3:30:05 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/18/2021 3:30:05 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[3/18/2021 3:30:06 AM] [ERROR] Failed to create MXF file. Exiting.
[3/18/2021 3:30:06 AM] [ INFO] epg123 update execution time was 00:00:03.6190000.
Can't say it happens often...

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.4 (64 bit)
Report Created on 03/18/2021 at 11:15:57
================================================================
     1 [4/13/2020 3:30:02 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     2 [4/13/2020 3:30:02 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     3 [4/13/2020 7:07:28 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     4 [4/13/2020 7:07:28 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     5 [4/13/2020 7:09:34 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     6 [4/13/2020 7:09:34 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     7 [4/13/2020 7:28:33 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     8 [4/13/2020 7:28:34 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
     9 [4/13/2020 8:04:28 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    10 [4/13/2020 8:04:29 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    11 [4/13/2020 8:18:01 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    12 [4/13/2020 8:18:01 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    13 [4/22/2020 3:30:04 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    14 [4/22/2020 3:30:05 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    15 [7/11/2020 3:30:24 AM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    16 [3/16/2021 3:30:03 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
    17 [3/18/2021 3:30:05 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log, trace20200713_173313.log, and trace20201130_080439.log
Search String:		[ INFO] SD API WebException Thrown
Date Range:		03/11/2020 thru 03/18/2021 (373 days)
Total results found:	17
Query time:		16 seconds

===== GENERAL INFORMATION ======================================
Log Path:		D:\epg123\
Logfile timespan:	3/11/2020 thru 3/18/2021 (373 days)
Total lines processed:	31983

Visit The Green Button at http://www.thegreenbutton.tv
Last edited by d00zah on Thu Mar 18, 2021 3:17 pm, edited 1 time in total.

Space

Posts: 2245
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#3

Post by Space » Thu Mar 18, 2021 3:08 pm

I've had the "Failed to retrieve token" error recently and when I asked Rob at Schedules Direct about it, he said "It's possible that you may have tried to access the service while it was in a scaling operation" and didn't really seem concerned about it.

I had just re-subscribed to the service and was testing to make sure it worked, so I tried several times that morning (between 4:14am ET and 4:50am ET, about an hour after the time change for Daylight Savings Time) and every time it got the same error. The next day, I tried it again in the afternoon and it worked fine.

User avatar
d00zah

Posts: 160
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#4

Post by d00zah » Fri Mar 19, 2021 12:45 pm

Faied again last night, but succeeded when run manually just now. Times are eastern US. Might be hitting a maintenance/peak usage window?

Code: Select all

[3/19/2021 3:30:04 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/19/2021 3:30:04 AM] [ERROR] Failed to complete request. Exiting
[3/19/2021 3:30:04 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/19/2021 3:30:04 AM] [ERROR] Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
[3/19/2021 3:30:04 AM] [ERROR] Failed to create MXF file. Exiting.

User avatar
StinkyImp

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

HTPC Specs: Show details

#5

Post by StinkyImp » Fri Mar 19, 2021 3:55 pm

d00zah wrote:
Fri Mar 19, 2021 12:45 pm
Faied again last night...
Me too. This is four nights in a row and very out of character with the error. In all previous instances it's cleared itself in (at most) two days.

Code: Select all

[3/19/2021 12:15:11 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout . Trying again.
[3/19/2021 12:15:11 AM] [ERROR] Failed to complete request. Exiting
[3/19/2021 12:15:11 AM] [ERROR] Did not receive a response from Schedules Direct for a token request.
[3/19/2021 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.
[3/19/2021 12:15:11 AM] [ERROR] Failed to create MXF file. Exiting.
I'll try a manual update and also change the task execution time.

Is anyone else experiencing this?

PS - That's a cool EPG123 log parser you're using! ;)

UPDATE: The manual update succeeded. Here's hoping the change in execution time overnight takes care of it.

Code: Select all

[3/19/2021 9:01:27 AM] ===============================================================================
[3/19/2021 9:01:27 AM]  Activating the epg123 configuration GUI. version 1.6.3.0
[3/19/2021 9:01:27 AM] ===============================================================================
[3/19/2021 9:01:28 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[3/19/2021 9:01:28 AM] [ INFO] Status request successful. account expires: 2022-02-12T14:47:08Z , lineups: 1/4 , lastDataUpdate: 2021-03-19T15:25:47Z
[3/19/2021 9:01:28 AM] [ INFO] system status: Online , message: No known issues.
[3/19/2021 9:01:28 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[3/19/2021 9:01:29 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-85003.
[3/19/2021 9:01:29 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 3/19/2021 12:14:59 AM; Exit: 0x00000000

User avatar
d00zah

Posts: 160
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#6

Post by d00zah » Fri Mar 19, 2021 4:14 pm

StinkyImp wrote:
Fri Mar 19, 2021 3:55 pm
PS - That's a cool EPG123 log parser you're using! ;)
I know dis guy... 8-)

Handy, as it shows 12 of my 17 occurrences were on 4/13/20, which appears to be a legit outage day. Makes the event REALLY infrequent. I, too, will try adjusting schedule timing should this persist.

User avatar
StinkyImp

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

HTPC Specs: Show details

#7

Post by StinkyImp » Fri Mar 19, 2021 6:21 pm

d00zah wrote:
Fri Mar 19, 2021 4:14 pm
StinkyImp wrote:
Fri Mar 19, 2021 3:55 pm
PS - That's a cool EPG123 log parser you're using! ;)
I know dis guy... 8-)
In case you're interested, the newest version is 1.7.6. :think:

User avatar
d00zah

Posts: 160
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#8

Post by d00zah » Fri Mar 19, 2021 8:36 pm

why, thank you!

User avatar
StinkyImp

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

HTPC Specs: Show details

#9

Post by StinkyImp » Sat Mar 20, 2021 3:18 pm

Failed again. That's five nights in a row. I've posted on the SD forums since it's the same every night... and they all seem to be associated with "a failure to communicate" with SD.

Code: Select all

SD API WebException Thrown. Message: The remote server returned an error
Failed to complete request. Exiting
Did not receive a response from Schedules Direct for a token request.
Failed to retrieve token from Schedules Direct. message: Did not receive a response from Schedules Direct for a token request.
Since it works with the "Save & Execute" command within EPG123, I know it can reach the SD API server. Weird :wtf:

glorp

Posts: 357
Joined: Sun Sep 23, 2012 2:54 pm
Location:

HTPC Specs: Show details

#10

Post by glorp » Sat Mar 20, 2021 4:15 pm

IIRC failed token request is what happens when your SD account already has an authenticated connection in use. You can use it on an unlimited number of WMC installations but you can only have one at a time pull data. If that's your case, schedule them at different times. It would make sense that it works for you when you do it manually too.

User avatar
d00zah

Posts: 160
Joined: Fri Nov 07, 2014 7:20 pm
Location:

HTPC Specs: Show details

#11

Post by d00zah » Sat Mar 20, 2021 5:23 pm

Mine failed every other night over the last 4. Manual update ~8-9AM always works after failed task. Adjusting task time as an experiment.

User avatar
StinkyImp

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

HTPC Specs: Show details

#12

Post by StinkyImp » Sun Mar 21, 2021 3:29 pm

Hmmm... Six days in a row now. I posted to the SD forums yesterday about this issue and their wording, "the SD system-check backend has also detected the issues" leads me to believe they're doing some type of maintenance or upgrades during my scheduled update window.

Image

That last part about changing my scheduled update time is something I wasn't wanting. Over the years I've set up various tasks centered around my daily SD update. Some occur before and some occur after. That means if I drastically change my SD update time, I have to change all the other tasks so they maintain their chain of operation. :crazy:

As RobertE said, "Hopefully RobertK will respond..." and then I can make all the scheduled changes once and be done with it!

User avatar
StinkyImp

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

HTPC Specs: Show details

#13

Post by StinkyImp » Sun Mar 21, 2021 3:33 pm

glorp wrote:
Sat Mar 20, 2021 4:15 pm
IIRC failed token request is what happens when your SD account already has an authenticated connection in use.
This isn't the case. EPG123 runs on one dedicated machine, the log files show it closing properly and Task Manager doesn't show any instances of it running. The SD API WebException also persists through reboots.

User avatar
StinkyImp

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

HTPC Specs: Show details

#14

Post by StinkyImp » Wed Mar 24, 2021 2:10 pm

Update from rkulagow at Schedules Direct...
  • I've added additional capacity to handle the surge that we're starting to see around midnight in certain timezones.
...and everything is back to normal. :)

Post Reply