No listings in guide - error messages in trace

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
colincliff

Posts: 4
Joined: Sun Sep 01, 2013 8:10 pm
Location:

HTPC Specs: Show details

No listings in guide - error messages in trace

#1

Post by colincliff » Sun Jul 17, 2016 6:27 pm

I have tried an initial run of EPG123 and am running in to the following error resulting in no listing in the guide. Am I doing something obviously wrong?

thanks in advance!

[17/07/2016 19:22:55] ====================== Beginning epg123 client execution. =====================
[17/07/2016 19:22:55] [ INFO] Import=True , Match=True , NoLogo=False
[17/07/2016 19:22:55] [ INFO] import filename = epg123.mxf
[17/07/2016 19:23:17] [ERROR] Error: The following error was encountered while processing the file. Aborting.
[17/07/2016 19:23:17] [ERROR] The string '2016-07-17T01:00' is not a valid AllXsd value.
[17/07/2016 19:23:18] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[17/07/2016 19:23:18] [ERROR] Failed to import .mxf file. Exiting.
[17/07/2016 19:23:18] [ INFO] Beginning cache cleanup routine.
[17/07/2016 19:23:19] [ INFO] 0 files deleted from the cache directory during cleanup.
[17/07/2016 19:23:19] [STATS] epg123 update execution time was 00:01:01.9351997.

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Sun Jul 17, 2016 6:42 pm

colincliff wrote:I have tried an initial run of EPG123 and am running in to the following error resulting in no listing in the guide. Am I doing something obviously wrong?

thanks in advance!

[17/07/2016 19:22:55] ====================== Beginning epg123 client execution. =====================
[17/07/2016 19:22:55] [ INFO] Import=True , Match=True , NoLogo=False
[17/07/2016 19:22:55] [ INFO] import filename = epg123.mxf
[17/07/2016 19:23:17] [ERROR] Error: The following error was encountered while processing the file. Aborting.
[17/07/2016 19:23:17] [ERROR] The string '2016-07-17T01:00' is not a valid AllXsd value.
[17/07/2016 19:23:18] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[17/07/2016 19:23:18] [ERROR] Failed to import .mxf file. Exiting.
[17/07/2016 19:23:18] [ INFO] Beginning cache cleanup routine.
[17/07/2016 19:23:19] [ INFO] 0 files deleted from the cache directory during cleanup.
[17/07/2016 19:23:19] [STATS] epg123 update execution time was 00:01:01.9351997.
First I've seen anything like this, and it's weird that the seconds is missing from the string. It should be '2016-07-17T01:00:00' which is probably why it is failing. This appears to be a SD problem, but to verify, could you let me know what lineup you are using so I can recreate it here?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

colincliff

Posts: 4
Joined: Sun Sep 01, 2013 8:10 pm
Location:

HTPC Specs: Show details

#3

Post by colincliff » Sun Jul 17, 2016 7:34 pm

Hi Garry, thanks for the reply. I'm using the 'Freesat - England (United Kingdom)' lineup.

thanks,

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Sun Jul 17, 2016 8:15 pm

Your offending station is channel 152 SD-True Crime +1 (SD-TRUECRIMEP1), serviceId 3099098. Right now, if you deselect that channel and run epg123 again, a proper mxf file will be generated and you should be good-to-go. This is a Schedules Direct issue (first I've seen), but I, of course, could screen for this scenario in epg123 as well.

Gist of problem, SD is supposed to supply the following:

Code: Select all

airDateTime - 20 characters. Mandatory. "2014-10-03T00:00:00Z". This will always be in "Z" time; your grabber must make any adjustments to localtime if it does not natively work in "Z" time internally.
... epg123 simply takes that input, strips off the ending 'Z', and puts that in the mxf. Evidently SD is not supplying the seconds for that particular station.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

colincliff

Posts: 4
Joined: Sun Sep 01, 2013 8:10 pm
Location:

HTPC Specs: Show details

#5

Post by colincliff » Sun Jul 17, 2016 8:47 pm

excellent, thanks so much. That did the trick!

rkulagow

Posts: 246
Joined: Sun Jul 19, 2015 1:04 am
Location: Schedules Direct

HTPC Specs: Show details

#6

Post by rkulagow » Mon Jul 18, 2016 3:13 am

Please check now.

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Mon Jul 18, 2016 3:31 am

rkulagow wrote:Please check now.
Having problems with schedule MD5s ... the correction not flow up correctly?
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

Post Reply