Today the downloading of EPG data into TV Scheduler Pro is failing. Tried it on 2 PCs. Same error.
Loading Data Please Wait...
About to load XMLTV Data from:
http://iceguide.icetv.com.au/cgi-bin/epg/i...uide&days=7
There was an error loading the XMLTV Data!
org.xml.sax.SAXParseException; lineNumber: 115; columnNumber: 30; The entity name must immediately follow the '&' in the entity reference.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at GuideStore.loadXMLdata(GuideStore.java:650)
at GuideStore.loadXMLTV(GuideStore.java:343)
at EpgDataRes.reloadXMLTVdata(EpgDataRes.java:1773)
at EpgDataRes.getResponse(EpgDataRes.java:49)
at HTTPRequest.sendResponseData(HTTPRequest.java:124)
at RequestObject.run(RequestObject.java:144)
at java.lang.Thread.run(Unknown Source)
EPG Data Load Failed!
After receiving the error I installed the latest Java and rebooted, but the error still occurs.
Has anything changed on the IceTV end?
Loading Data Please Wait...
About to load XMLTV Data from:
http://iceguide.icetv.com.au/cgi-bin/epg/i...uide&days=7
There was an error loading the XMLTV Data!
org.xml.sax.SAXParseException; lineNumber: 115; columnNumber: 30; The entity name must immediately follow the '&' in the entity reference.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at GuideStore.loadXMLdata(GuideStore.java:650)
at GuideStore.loadXMLTV(GuideStore.java:343)
at EpgDataRes.reloadXMLTVdata(EpgDataRes.java:1773)
at EpgDataRes.getResponse(EpgDataRes.java:49)
at HTTPRequest.sendResponseData(HTTPRequest.java:124)
at RequestObject.run(RequestObject.java:144)
at java.lang.Thread.run(Unknown Source)
EPG Data Load Failed!
After receiving the error I installed the latest Java and rebooted, but the error still occurs.
Has anything changed on the IceTV end?