Failed to parse

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

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

HTPC Specs: Show details

Failed to parse

#1

Post by StinkyImp » Fri Mar 23, 2018 5:14 pm

This inquiry is solely out of curiosity because it doesn't appear to have any ill effects. I noticed a bunch popped up in the channel 7.4 debacle. It just seems to occur out of the blue and I'm wondering what it is.

Occasionally I receive a "Failed to parse" entry in the log. They seem to sporadically reoccur for the same station ID but there's no rhyme or reason for them. Maybe someone else will see them and wonder what they are?

Thanks for your sage wisdom!
Failed to parse.png

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Fri Mar 23, 2018 10:53 pm

The "Failed to parse" error is due to the response from Schedules Direct for that particular station have no information ... basically a null. In the past this has been attributed to SD's batch updates/downloads from Gracenote being in progress or was a failed update.

What this means for you guide is those stations did not get any updated information. If you were doing a fresh install/database, it means those stations would not have any guide information at all. As you can see, the problem is cleared next update... actually, the problem is cleared next update for SD which I believe now happens every 12 hours (used to be 6 hours).
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply