Failed to parse

An evolving, supported alternative to Rovi
Important Information
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf

Failed to parse

Post#1 » 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
StinkyImp
 
Posts: 100
Joined: 11 May 2017
HTPC Specs: Show details

Post#2 » 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).
User avatar
garyan2
 
Posts: 2762
Joined: 27 November 2015
HTPC Specs: Show details
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net


Return to EPG123



Who is online

Users browsing this forum: No registered users and 1 guest

cron