Getting Error Messages trying to update after upgrade

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
whealthy

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

HTPC Specs: Show details

Getting Error Messages trying to update after upgrade

#1

Post by whealthy » Fri Dec 06, 2019 5:00 am

I was using 1.2.3 tried to load up a lineup but no channels appeared. So I thought maybe I should upgrade and now I cant even subscribe to a lineup now after selecting "Apply and Exit". I just see the red dot at the top I finally upgraded to 1.3 and now I can't load a lineup. I select a lineup and then select "apply & Exit" and nothing happens. The log shows the following errors:

[12/5/2019 8:34:34 PM] [ERROR] Failed to get a response from Schedules Direct when trying to add lineup USA-WA63873-X.
[12/5/2019 8:34:34 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:34:34 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:34:34Z
[12/5/2019 8:34:35 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:34:35 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:34:35Z
[12/5/2019 8:34:35 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:34:35 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:34:35Z
[12/5/2019 8:34:35 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:34:35 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:34:35Z
[12/5/2019 8:34:35 PM] [ERROR] Failed to complete request. Exiting
[12/5/2019 8:34:35 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[12/5/2019 8:35:00 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:00 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:34:59Z
[12/5/2019 8:35:00 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:00 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:00Z
[12/5/2019 8:35:00 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:00 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:00Z
[12/5/2019 8:35:00 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:00 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:00Z
[12/5/2019 8:35:00 PM] [ERROR] Failed to complete request. Exiting
[12/5/2019 8:35:00 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.
[12/5/2019 8:35:04 PM] [ INFO] Successfully retrieved list of available countries from Schedules Direct.
[12/5/2019 8:35:04 PM] [ INFO] Successfully retrieved the headends for USA and postal code 98072.
[12/5/2019 8:35:17 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[12/5/2019 8:35:17 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:17Z
[12/5/2019 8:35:17 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[12/5/2019 8:35:17 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:17Z
[12/5/2019 8:35:18 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[12/5/2019 8:35:18 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:18 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (403) Forbidden. , Status: ProtocolError
[12/5/2019 8:35:18 PM] [ INFO] SD responded with error code: 4100 , message: Exceeded maximum number of lineup changes for today. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:18 PM] [ERROR] Failed to complete request. Exiting
[12/5/2019 8:35:18 PM] [ERROR] Failed to get a response from Schedules Direct when trying to add lineup USA-WA63873-X.
[12/5/2019 8:35:18 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:18 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:18 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:18 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:18 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:18 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:19 PM] [ INFO] SD API WebException Thrown. Message: The remote server returned an error: (400) Bad Request. , Status: ProtocolError
[12/5/2019 8:35:19 PM] [ INFO] SD responded with error code: 4102 , message: No lineups have been added to this account. , serverID: 20141201.web.1 , datetime: 2019-12-06T04:35:18Z
[12/5/2019 8:35:19 PM] [ERROR] Failed to complete request. Exiting
[12/5/2019 8:35:19 PM] [ERROR] Did not receive a response from Schedules Direct for a client lineup listings.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Fri Dec 06, 2019 5:10 am

Interesting. The preview for that lineup shows all your channels, but after adding it there are no channels in the data. I've seen this before and the problem is with Schedules Direct. You will have to open a ticket with them to get it corrected.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

glorp

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

HTPC Specs: Show details

#3

Post by glorp » Fri Dec 06, 2019 3:54 pm

Gary I'm seeing something similar. The regularly scheduled run this morning failed on the first attempt to build a line up and crashed. When I saw the log error I pulled up the GUI on the server. That's the second run and the GUI had my regular line up shown after login but no channels for it shown in the GUI. A few minutes later tried again and the GUI was showing line up + channels now. So I ran a full schedule download which was uneventful. All in the log.

Is this SD or lack of EPG123 timing/error recovery?

Code: Select all

[12/6/2019 6:00:02 AM] ===============================================================================
[12/6/2019 6:00:02 AM]  Beginning epg123 update execution. version 1.2.22.0
[12/6/2019 6:00:02 AM] ===============================================================================
[12/6/2019 6:00:02 AM] [ INFO] Beginning EPG123 update execution. 2019-12-06 14:00:02Z
[12/6/2019 6:00:02 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : False , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: False , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[12/6/2019 6:00:03 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[12/6/2019 6:00:03 AM] [ INFO] Status request successful. account expires: 2020-03-07T14:42:58Z , lineups: 1/4 , lastDataUpdate: 2019-12-06T13:38:31Z
[12/6/2019 6:00:03 AM] [ INFO] system status: Online , message: No known issues.
[12/6/2019 6:00:03 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.0 and can be downloaded from http://epg123.garyan2.net.
[12/6/2019 6:00:04 AM] [ INFO] Successfully retrieved TMDb configurations.
[12/6/2019 6:00:04 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[12/6/2019 6:00:04 AM] Entering buildLineupServices() for 1 lineups.
[12/6/2019 6:00:05 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[12/6/2019 6:00:05 AM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-XXXXXXX-X.
[12/6/2019 6:00:05 AM] [ERROR] There are 0 stations queued for download from 1 subscribed lineups. Exiting.
[12/6/2019 6:00:05 AM] [ERROR] Check that lineups are 'INCLUDED' and stations are selected in the EPG123 GUI.
[12/6/2019 6:00:05 AM] [ERROR] Failed to create MXF file. Exiting.
[12/6/2019 6:00:05 AM] [ INFO] epg123 update execution time was 00:00:02.8976965.
[12/6/2019 6:45:39 AM] ===============================================================================
[12/6/2019 6:45:39 AM]  Activating the epg123 configuration GUI. version 1.2.22.0
[12/6/2019 6:45:39 AM] ===============================================================================
[12/6/2019 6:45:40 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.0 and can be downloaded from http://epg123.garyan2.net.
[12/6/2019 6:45:41 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 12/6/2019 6:00:01 AM; Exit: 0x00000000
[12/6/2019 6:45:41 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[12/6/2019 6:45:42 AM] [ INFO] Status request successful. account expires: 2020-03-07T14:42:58Z , lineups: 1/4 , lastDataUpdate: 2019-12-06T13:38:31Z
[12/6/2019 6:45:42 AM] [ INFO] system status: Online , message: No known issues.
[12/6/2019 6:45:42 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[12/6/2019 6:45:42 AM] [ERROR] SD API Unknown exception thrown. Message: Unable to read data from the transport connection: The connection was closed.
[12/6/2019 6:45:42 AM] [ERROR] Did not receive a response from Schedules Direct for retrieval of lineup USA-XXXXXXX-X.
[12/6/2019 6:48:14 AM] ===============================================================================
[12/6/2019 6:48:14 AM]  Activating the epg123 configuration GUI. version 1.2.22.0
[12/6/2019 6:48:14 AM] ===============================================================================
[12/6/2019 6:48:15 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.0 and can be downloaded from http://epg123.garyan2.net.
[12/6/2019 6:48:15 AM] [ INFO] Successfully queried the Task Scheduler for status. Ready. Last Run 12/6/2019 6:00:01 AM; Exit: 0x00000000
[12/6/2019 6:48:16 AM] [ INFO] Token request successful. serverID: 20141201.web.1
[12/6/2019 6:48:16 AM] [ INFO] Status request successful. account expires: 2020-03-07T14:42:58Z , lineups: 1/4 , lastDataUpdate: 2019-12-06T13:38:31Z
[12/6/2019 6:48:16 AM] [ INFO] system status: Online , message: No known issues.
[12/6/2019 6:48:16 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[12/6/2019 6:48:17 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-XXXXXXX-X.
[12/6/2019 6:48:28 AM] ===============================================================================
[12/6/2019 6:48:28 AM]  Beginning epg123 update execution. version 1.2.22.0
[12/6/2019 6:48:28 AM] ===============================================================================
[12/6/2019 6:48:28 AM] [ INFO] Beginning EPG123 update execution. 2019-12-06 14:48:28Z
[12/6/2019 6:48:28 AM] [ INFO] DaysToDownload: 14 , TheTVDBNumbers : False , PrefixEpisodeTitle: False , PrefixEpisodeDescription : False , AppendEpisodeDesc: True , OADOverride : True , TMDbCoverArt: False , IncludeSDLogos : False , AutoAddNew: True , CreateXmltv: False , ModernMediaUiPlusSupport: False
[12/6/2019 6:48:28 AM] [ INFO] Status request successful. account expires: 2020-03-07T14:42:58Z , lineups: 1/4 , lastDataUpdate: 2019-12-06T13:38:31Z
[12/6/2019 6:48:28 AM] [ INFO] system status: Online , message: No known issues.
[12/6/2019 6:48:28 AM] [ INFO] epg123 is not up to date. Latest version is 1.3.0 and can be downloaded from http://epg123.garyan2.net.
[12/6/2019 6:48:28 AM] [ INFO] Successfully retrieved TMDb configurations.
[12/6/2019 6:48:28 AM] [ INFO] Successfully requested listing of client lineups from Schedules Direct.
[12/6/2019 6:48:28 AM] Entering buildLineupServices() for 1 lineups.
[12/6/2019 6:48:29 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-XXXXXXX-X.
[12/6/2019 6:48:29 AM] Exiting buildLineupServices(). SUCCESS.
[12/6/2019 6:48:29 AM] Entering getAllScheduleEntryMd5s() for 14 days on 521 stations.

<SNIP>

[12/6/2019 7:00:34 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[12/6/2019 7:00:34 AM] [ INFO] epg123 update execution time was 00:12:06.0795653.

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Fri Dec 06, 2019 4:16 pm

SD corrected a problem with one of their servers earlier this morning. I had sent SD an email at 06:50 your time and literally 2 minutes later, they had responded that they kicked the server and everything was back up and running. Whether they were already fixing it when I sent the email, or they are just that dang fast, I don't know. But like you, I verified the problem with my lineup at 06:35 and back in business at 06:52.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

glorp

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

HTPC Specs: Show details

#5

Post by glorp » Fri Dec 06, 2019 4:48 pm

k, good enough.

thanks. :)

whealthy

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

HTPC Specs: Show details

#6

Post by whealthy » Fri Dec 06, 2019 11:59 pm

Still not working for me. :!:

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Sat Dec 07, 2019 12:13 am

I am seeing all your channels in EPG123 Configuration and just download a days worth of listings for all stations... so working here.

When you were trying to get it to work yesterday, you may have configured it to download 0 stations. I would suggest opening the configuration GUI and make sure everything looks okay.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

whealthy

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

HTPC Specs: Show details

#8

Post by whealthy » Sat Dec 07, 2019 12:19 am

Since upgrading I haven;t been able to even subscribe to a lineup. Every time I would "Apply and Exit" nothing would happen. I just tried it before I wrote that last message. Now I tried it again and I can't get even get any lineups to list. I get a pop up that says "No headers found for postal code or country"

whealthy

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

HTPC Specs: Show details

#9

Post by whealthy » Sat Dec 07, 2019 12:22 am

Now it is working. I had just submitted a ticket to SD a minute before my last entry.

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Sat Dec 07, 2019 12:27 am

Wow, rkulagow is on it today... that is quick service. I take it you didn't submit the ticket last night? :clap:
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

whealthy

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

HTPC Specs: Show details

#11

Post by whealthy » Sat Dec 07, 2019 12:33 am

When I submitted the ticket, there was a banner that gave a Warning, that SD=JSON couldn't be Fetched, or something along that line, on the Lineup Support page. I just looked back and the banner is gone now.

User avatar
garyan2

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

HTPC Specs: Show details

#12

Post by garyan2 » Sat Dec 07, 2019 12:38 am

I wonder what the odds are that they schedule a maintenance downtime this weekend... we shall see.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply