All channels missing from Lineup

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
rimmel

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

HTPC Specs: Show details

All channels missing from Lineup

#1

Post by rimmel » Thu Jul 25, 2019 1:16 am

I just attempted to run epg123 and it said that all the channels are missing from one of my lineups. The other lineup has all the correct channels but epg123 errors out with some sort of transport error during "getMd5ScheduleEntries" if I try to update that second lineup. If I login to my SD account it says that both my lineups are correctly populated with channels. Does this just mean that SD is down or does epg123 have a problem?

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Thu Jul 25, 2019 1:38 am

I get the same error. Please open a ticket with Schedules Direct.

Code: Select all

Unable to read data from the transport connection: The connection was closed.
Note that the website only shows you the XML server (SD-DD) and not the JSON server (SD-JSON). Seeing the correct information on the SD-DD side doesn't mean the SD-JSON side has the same status.

EDIT: I should note that you need to apply the ticket to your USA-WA46544-X lineup.
Last edited by garyan2 on Thu Jul 25, 2019 1:59 am, edited 1 time in total.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

rimmel

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

HTPC Specs: Show details

#3

Post by rimmel » Thu Jul 25, 2019 1:54 am

SD ticket submitted!

whealthy

Posts: 12
Joined: Fri Jul 05, 2019 10:28 pm
Location:

HTPC Specs: Show details

#4

Post by whealthy » Thu Jul 25, 2019 2:01 am

I tried to install the new version on another machine and the lineup I want shows up but when I check the box and click on Apply & Exit, nothing happens. No channels are downloaded.

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Thu Jul 25, 2019 2:11 am

Check what box? and is the lineup included in the download (green dot in top left corner of the lineup tab)?

A look at your trace.log file will help.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Thu Jul 25, 2019 2:19 am

Something funny is going on with SD and lineups. I'm seeing multiple lineups that are responding with nothing. I even had 1 working 15 minutes ago, but now is not.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

whealthy

Posts: 12
Joined: Fri Jul 05, 2019 10:28 pm
Location:

HTPC Specs: Show details

#7

Post by whealthy » Thu Jul 25, 2019 2:27 am

After posting, I tried it again and successfully downloaded the lineup. But when I went to exit out, I was told I hadn't scheduled an update so I went to schedule the update and my lineup disappeared. Looking at the log, there is one instance where it shows I retrieved the lineup successfully but all others show an error message of no reply from Schedules direct.

What box checked?
When I click on Lineups, a window pops up showing the lineup I had previously selected with a checkbox next to it. That is the box I checked. Then I pressed the Apply & Exit.

User avatar
garyan2

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

HTPC Specs: Show details

#8

Post by garyan2 » Thu Jul 25, 2019 2:37 am

whealthy wrote:
Thu Jul 25, 2019 2:27 am
When I click on Lineups, a window pops up showing the lineup I had previously selected with a checkbox next to it. That is the box I checked. Then I pressed the Apply & Exit.
Yah, I figured that out. That check box is only for when you want to [Remove Selected]... it does nothing for the adding lineups. No harm, though.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

whealthy

Posts: 12
Joined: Fri Jul 05, 2019 10:28 pm
Location:

HTPC Specs: Show details

#9

Post by whealthy » Thu Jul 25, 2019 2:48 am

I got the .mxf file from my other machine and did a manual import. It imported all the channels fine.

When I did this (manually imported a previously downloaded .mxf file) on tmy first computer, no channels showed up in the guide. I had to open up the Client and match the channels up and Subscribe to get the left and right hand sides of the screens to be linked. What did I do wrong to make this happen and is there a way now to get the channels all linked up without having to highlight the individual channels on each side and right click/Subscribe?
Thanks for your help.

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Thu Jul 25, 2019 2:54 am

With a manual import, there is no automatch routine. What there is though, is a button to Match by: [# Number] on the left side that will do all the work for you. You won't have to highlight the left and right side channels to subscribe manually.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Sammy2

Posts: 1670
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#11

Post by Sammy2 » Thu Jul 25, 2019 3:04 am

Maybe I should have read the forums first??

I finally had a bit of time to do some channel matching and combining and deleting between my Prime and Quatro Tuners and ran across issues trying to get my lineups to load. I fear I'll have no guide tomorrow if tonight's run doesn't create a usable epg123.xmltv. I think I'll archive the last known good one to load tomorrow morning but why tonight?!?! I have the time but not the tools. WAA! :cry: :cry:

Code: Select all

7/24/2019 7:29:20 PM] ===============================================================================
[7/24/2019 7:29:20 PM]  Activating the epg123 client GUI. version 1.2.14.0
[7/24/2019 7:29:20 PM] ===============================================================================
[7/24/2019 7:29:21 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:38:54 PM] ===============================================================================
[7/24/2019 7:38:54 PM]  Activating the epg123 client GUI. version 1.2.14.0
[7/24/2019 7:38:54 PM] ===============================================================================
[7/24/2019 7:38:54 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:39:05 PM] ===============================================================================
[7/24/2019 7:39:05 PM]  Activating the epg123 configuration GUI. version 1.2.14.0
[7/24/2019 7:39:05 PM] ===============================================================================
[7/24/2019 7:39:06 PM] [ INFO] epg123 is not up to date. Latest version is 1.2.15 and can be downloaded from http://epg123.garyan2.net.
[7/24/2019 7:39:06 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:39:06 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:39:06 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 2/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:39:06 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:39:06 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:39:07 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:39:07 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:39:08 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:39:51 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:40:04 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:40:04 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:40:04 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:40:05 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:40:56 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:41:09 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:41:09 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:41:09 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:41:10 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:41:38 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:41:44 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:41:44 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:42:04 PM] [ INFO] Successfully retrieved the channels in lineup USA-CA04768-X for preview.
[7/24/2019 7:42:21 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:42:22 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:42:22 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:42:23 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:43:14 PM] ===============================================================================
[7/24/2019 7:43:14 PM]  Activating the epg123 client GUI. version 1.2.14.0
[7/24/2019 7:43:14 PM] ===============================================================================
[7/24/2019 7:43:14 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:43:22 PM] ===============================================================================
[7/24/2019 7:43:22 PM]  Activating the epg123 configuration GUI. version 1.2.14.0
[7/24/2019 7:43:22 PM] ===============================================================================
[7/24/2019 7:43:23 PM] [ INFO] epg123 is not up to date. Latest version is 1.2.15 and can be downloaded from http://epg123.garyan2.net.
[7/24/2019 7:43:23 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:43:24 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:43:24 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 2/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:43:24 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:43:24 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:43:25 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:43:25 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:43:25 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:43:35 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:43:43 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:43:43 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:43:43 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:43:44 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:43:57 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:43:59 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:43:59 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:44:33 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:44:36 PM] [ INFO] Successfully retrieved the channels in lineup USA-CA04768-X for preview.
[7/24/2019 7:44:57 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:44:58 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:45:06 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:45:06 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04768-X.
[7/24/2019 7:45:06 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:49:14 PM] ===============================================================================
[7/24/2019 7:49:14 PM]  Activating the epg123 configuration GUI. version 1.2.15.0
[7/24/2019 7:49:14 PM] ===============================================================================
[7/24/2019 7:49:16 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:49:16 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:49:16 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 2/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:49:16 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:49:16 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:49:17 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:49:17 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:49:17 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:49:20 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:49:28 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:49:32 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:49:32 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:49:40 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:49:41 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:49:41 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:49:41 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:49:48 PM] ===============================================================================
[7/24/2019 7:49:48 PM]  Activating the epg123 configuration GUI. version 1.2.15.0
[7/24/2019 7:49:48 PM] ===============================================================================
[7/24/2019 7:49:49 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:49:49 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:49:49 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 2/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:49:49 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:49:49 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:49:50 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:49:50 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:49:51 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:49:54 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:02 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:50:03 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:50:11 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:11 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:50:11 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:50:12 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:50:30 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:35 PM] [ INFO] Successfully removed lineup USA-CA04768-X from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 6
[7/24/2019 7:50:35 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:35 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:50:37 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:38 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:50:38 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:50:47 PM] [ INFO] Successfully added lineup USA-CA04768-X to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 5
[7/24/2019 7:50:47 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:50:47 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:50:47 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:50:48 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:51:03 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:51:08 PM] [ INFO] Successfully removed lineup USA-CA04768-X from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 5
[7/24/2019 7:51:08 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:51:08 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:51:14 PM] ===============================================================================
[7/24/2019 7:51:14 PM]  Activating the epg123 configuration GUI. version 1.2.15.0
[7/24/2019 7:51:14 PM] ===============================================================================
[7/24/2019 7:51:14 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:51:15 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:51:16 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 1/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:51:16 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:51:16 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:51:16 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:51:19 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:51:20 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:51:21 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:51:28 PM] [ INFO] Successfully added lineup USA-CA04768-X to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 4
[7/24/2019 7:51:28 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:51:30 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:51:30 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:51:30 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:54:00 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:54:08 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:54:09 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:54:09 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:54:09 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:54:13 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:54:20 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:54:20 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:54:27 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:54:27 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:54:33 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:54:34 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:54:51 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:54:52 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:54:52 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:54:52 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:55:39 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:55:42 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:55:43 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:55:43 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:55:43 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:55:46 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:55:52 PM] [ INFO] Successfully removed lineup USA-CA04768-X from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 4
[7/24/2019 7:55:53 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:55:53 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:55:54 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:55:57 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:55:58 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:56:32 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:56:32 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:56:38 PM] [ INFO] Successfully added lineup USA-CA04768-X to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 3
[7/24/2019 7:56:38 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:56:38 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:56:38 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:56:38 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:56:47 PM] ===============================================================================
[7/24/2019 7:56:47 PM]  Activating the epg123 configuration GUI. version 1.2.15.0
[7/24/2019 7:56:47 PM] ===============================================================================
[7/24/2019 7:56:48 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:56:49 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:56:49 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 2/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:56:49 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:56:49 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:56:49 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:56:49 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:56:50 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:57:07 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:57:16 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:57:17 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:57:17 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:57:17 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:57:20 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:57:30 PM] [ INFO] Successfully removed lineup USA-CA04768-X from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 3
[7/24/2019 7:57:30 PM] [ INFO] Successfully removed lineup USA-OTA-92508 from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 3
[7/24/2019 7:57:30 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:30 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:29Z
[7/24/2019 7:57:30 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:30 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:29Z
[7/24/2019 7:57:30 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:30 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:29Z
[7/24/2019 7:57:30 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:30 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:29Z
[7/24/2019 7:57:30 PM] [ERROR] Failed to complete request. Exiting
[7/24/2019 7:57:30 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[7/24/2019 7:57:35 PM] ===============================================================================
[7/24/2019 7:57:35 PM]  Activating the epg123 configuration GUI. version 1.2.15.0
[7/24/2019 7:57:35 PM] ===============================================================================
[7/24/2019 7:57:36 PM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 7/24/2019 2:15:00 AM; Exit: 0x00000000
[7/24/2019 7:57:36 PM] [ INFO] Token request successful. serverID: 20141201.web.1
[7/24/2019 7:57:37 PM] [ INFO] Status request successful. account expires: 2020-07-13T21:52:59Z , lineups: 0/4 , lastDataUpdate: 2019-07-24T19:33:01Z
[7/24/2019 7:57:37 PM] [ INFO] system status: Online , message: No known issues.
[7/24/2019 7:57:42 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:42 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:41Z
[7/24/2019 7:57:42 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:42 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:41Z
[7/24/2019 7:57:42 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:42 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:41Z
[7/24/2019 7:57:42 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:57:42 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:57:41Z
[7/24/2019 7:57:42 PM] [ERROR] Failed to complete request. Exiting
[7/24/2019 7:57:42 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[7/24/2019 7:57:45 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:57:45 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:57:47 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:57:56 PM] [ INFO] Successfully added lineup USA-CA04768-X to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 2
[7/24/2019 7:57:56 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:57:56 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:57:56 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:57:57 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:57:57 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-CA04768-X.
[7/24/2019 7:58:00 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:02 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:58:02 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:58:16 PM] [ INFO] Successfully added lineup USA-OTA-92508 to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 1
[7/24/2019 7:58:16 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:16 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:58:16 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:58:17 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:58:27 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:37 PM] [ INFO] Successfully removed lineup USA-OTA-92508 from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 1
[7/24/2019 7:58:37 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:38 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:58:38 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:58:47 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:50 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:58:50 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:58:50 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:59:08 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:14 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:15 PM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[7/24/2019 7:59:15 PM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-CA04768-X.
[7/24/2019 7:59:18 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:25 PM] [ INFO] Successfully removed lineup USA-CA04768-X from account. serverID: 20141201.web.1 , message: Deleted lineup. , changesRemaining: 1
[7/24/2019 7:59:25 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:25 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:24Z
[7/24/2019 7:59:26 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:26 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:25Z
[7/24/2019 7:59:26 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:26 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:25Z
[7/24/2019 7:59:26 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:26 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:25Z
[7/24/2019 7:59:26 PM] [ERROR] Failed to complete request. Exiting
[7/24/2019 7:59:26 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[7/24/2019 7:59:27 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:27 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:26Z
[7/24/2019 7:59:27 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:27 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:26Z
[7/24/2019 7:59:27 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:27 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:26Z
[7/24/2019 7:59:27 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[7/24/2019 7:59:27 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:26Z
[7/24/2019 7:59:27 PM] [ERROR] Failed to complete request. Exiting
[7/24/2019 7:59:27 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[7/24/2019 7:59:29 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:59:29 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:59:36 PM] [ INFO] Successfully added lineup USA-OTA-92508 to account. serverID: 20141201.web.1 , message: Added lineup. , changesRemaining: 0
[7/24/2019 7:59:36 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:37 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.
[7/24/2019 7:59:40 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:41 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[7/24/2019 7:59:41 PM] [ INFO] Successfully retrieved the headends for USA and postal code 92508.
[7/24/2019 7:59:48 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[7/24/2019 7:59:48 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:47Z
[7/24/2019 7:59:49 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[7/24/2019 7:59:49 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:48Z
[7/24/2019 7:59:49 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[7/24/2019 7:59:49 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:48Z
[7/24/2019 7:59:49 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[7/24/2019 7:59:49 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-07-25T02:59:48Z
[7/24/2019 7:59:49 PM] [ERROR] Failed to complete request. Exiting
[7/24/2019 7:59:49 PM] [ERROR] Failed to get a response from Schedules Direct when trying to add lineup USA-CA04768-X.
[7/24/2019 7:59:50 PM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[7/24/2019 7:59:51 PM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-92508.

whealthy

Posts: 12
Joined: Fri Jul 05, 2019 10:28 pm
Location:

HTPC Specs: Show details

#12

Post by whealthy » Thu Jul 25, 2019 3:13 am

Ok. Not sure what happened. All I did was manual import this time and the guide was all there and it wouldn't let me highlight both sides and click subscribe. I didn't press the Match by on the left side and when i went to the guide all the channels were there complete with programming. I mistakenly said "no channels showed up in the guide" for the first computer in the previous post but they did, there was just no programming. All the channels said, "No data available". When I linked some of the channels individually, the programming for the linked channels,then, showed up. That didn't happen this time. I manually imported and all the channels with programming were complete.

Sammy2

Posts: 1670
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#13

Post by Sammy2 » Thu Jul 25, 2019 3:16 am

I just disabled the nightly Refresh Lineup Task in Emby so I'll stick with the data I have but man this set me back! Guess I'll just focus on the Freeway Series between the Anaheim Angels and the Los Angeles Dodgers.

rimmel

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

HTPC Specs: Show details

#14

Post by rimmel » Thu Jul 25, 2019 6:56 am

I have received no response from my SD ticket regarding this problem. There is nothing on the SD site regarding an outage. I still have no channels in one of my lineups. Does anyone have any news about what is going on here?

Sammy2

Posts: 1670
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#15

Post by Sammy2 » Thu Jul 25, 2019 10:57 am

I'm pretty sure the two guys running Schedules Direct needed some sleep too!

Sammy2

Posts: 1670
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#16

Post by Sammy2 » Thu Jul 25, 2019 11:43 am

I see that with all the errors in last nights epg123 run, the mxf and xmltv files both have yesterday's date. No new ones were generated even though I have OTA lineup. I did notice that when exiting epg123 it told me no channels were selected which is odd.
trace (2).zip
(7.31 KiB) Downloaded 6 times

User avatar
garyan2

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

HTPC Specs: Show details

#17

Post by garyan2 » Thu Jul 25, 2019 1:50 pm

rimmel wrote:
Thu Jul 25, 2019 6:56 am
I have received no response from my SD ticket regarding this problem. There is nothing on the SD site regarding an outage. I still have no channels in one of my lineups. Does anyone have any news about what is going on here?
SD was working on it last night and asked to check the lineups on our end. All the lineups I checked last night (your guy's lineups) that were failing are now working. You should be able to complete a manual update (Save & Execute).
Sammy2 wrote:
Thu Jul 25, 2019 11:43 am
I see that with all the errors in last nights epg123 run, the mxf and xmltv files both have yesterday's date. No new ones were generated even though I have OTA lineup. I did notice that when exiting epg123 it told me no channels were selected which is odd.
trace (2).zip
Your OTA lineup is EXCLUDED, meaning the bubble on the top left of the lineup tab in the configuration GUI is red. You need to include it and Save. Also, since you kept deleting and adding back in your cable lineup, you exceed the number of ADDS allowed in a 24 hour period. You will either have to wait until tonight to add it back in, or contact SD and ask them to help with that.

Your automatch routine is throwing a lot of skipped matching messages. Do you understand the cause of that?
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
StinkyImp

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

HTPC Specs: Show details

#18

Post by StinkyImp » Thu Jul 25, 2019 5:24 pm

Since February 2017 I have received 14 "SD API WebExceptions". In every case they've cleared themselves within a day (or two) with no intervention by me.

If SD has been made aware of this situation, it should clear pretty quickly. I don't think there's anything we can do on "our side" to alleviate this.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.3 (64 bit)
Report Created on 07/25/2019 at 10:18:35
================================================================
     1 [2/5/2017 9:35:32 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
     2 [2/22/2017 2:05:16 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     3 [2/22/2017 2:12:02 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     4 [2/23/2017 2:02:32 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     5 [2/23/2017 2:10:20 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     6 [8/12/2017 2:00:11 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     7 [8/18/2017 2:00:23 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     8 [3/2/2018 12:15:20 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     9 [3/18/2018 12:15:38 AM] [ERROR] SD API WebException Thrown. Message: The underlying connection was closed: An unexpected error occurred on a receive. , Status: ReceiveFailure
    10 [6/5/2018 12:15:08 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    11 [9/25/2018 12:15:08 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
    12 [1/8/2019 12:18:01 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
    13 [2/8/2019 12:17:43 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    14 [7/25/2019 12:15:13 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log, trace_2017-2018.log, and trace_2019.log
Search String:		SD API WebException
Date Range:		02/05/2017 thru 07/25/2019 (901 days)
Total results found:	14
Now that this has been reported to SD, patience is our only recourse! :)

rimmel

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

HTPC Specs: Show details

#19

Post by rimmel » Thu Jul 25, 2019 10:20 pm

It looks like my lineups are OK now. I also received a response to my SD ticket this afternoon. Thanks for all of your help!

Sammy2

Posts: 1670
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

#20

Post by Sammy2 » Thu Jul 25, 2019 11:13 pm

StinkyImp wrote:Since February 2017 I have received 14 "SD API WebExceptions". In every case they've cleared themselves within a day (or two) with no intervention by me.

If SD has been made aware of this situation, it should clear pretty quickly. I don't think there's anything we can do on "our side" to alleviate this.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.3 (64 bit)
Report Created on 07/25/2019 at 10:18:35
================================================================
     1 [2/5/2017 9:35:32 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
     2 [2/22/2017 2:05:16 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     3 [2/22/2017 2:12:02 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     4 [2/23/2017 2:02:32 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     5 [2/23/2017 2:10:20 AM] [ERROR] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
     6 [8/12/2017 2:00:11 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     7 [8/18/2017 2:00:23 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     8 [3/2/2018 12:15:20 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
     9 [3/18/2018 12:15:38 AM] [ERROR] SD API WebException Thrown. Message: The underlying connection was closed: An unexpected error occurred on a receive. , Status: ReceiveFailure
    10 [6/5/2018 12:15:08 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    11 [9/25/2018 12:15:08 AM] [ERROR] SD API WebException Thrown. Message: The remote name could not be resolved: 'json.schedulesdirect.org' , Status: NameResolutionFailure
    12 [1/8/2019 12:18:01 AM] [ INFO] SD API WebException Thrown. Message: The operation has timed out , Status: Timeout
    13 [2/8/2019 12:17:43 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError
    14 [7/25/2019 12:15:13 AM] [ERROR] SD API WebException Thrown. Message: The remote server returned an error: (500) Internal Server Error. , Status: ProtocolError

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log, trace_2017-2018.log, and trace_2019.log
Search String:		SD API WebException
Date Range:		02/05/2017 thru 07/25/2019 (901 days)
Total results found:	14
Now that this has been reported to SD, patience is our only recourse! :)
Your tool is pretty cool.. thanks!

Sent from my SM-G960U1 using Tapatalk


Post Reply