[WARNG] The imported MXF file contained a WARNING in its status field

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: http://epg123.garyan2.net <> Setup guide here: http://epg123.garyan2.net/downloads/epg123_Guide.pdf
Post Reply
Sammy2

Posts: 1666
Joined: Fri Aug 24, 2012 7:35 pm
Location:

HTPC Specs: Show details

[WARNG] The imported MXF file contained a WARNING in its status field

#1

Post by Sammy2 » Wed Aug 14, 2019 10:48 am

In my log but everything else seems fine but I do have a lot of automatch messages.
Guide End Date CableTV.JPG
Guide End Date and Time CableTV
Guide End Date OTA.JPG
Guide End Date and Time OTA
trace.7z
Trace Log
(52.25 KiB) Downloaded 5 times

User avatar
StinkyImp

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

HTPC Specs: Show details

#2

Post by StinkyImp » Wed Aug 14, 2019 1:53 pm

Your "warnings" are all attributable to a "Failed to parse the schedule Md5 return for stationId XXXX" warning.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.4 (64 bit)
Report Created on 08/14/2019 at 06:45:26
================================================================
     1 [8/8/2019 2:15:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 83481 (KPXNDT6) on 2019-08-08 and after.
     2 [8/8/2019 2:25:34 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
     3 [8/10/2019 2:15:18 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 10367 (KCBS) on 2019-08-10 and after.
     4 [8/10/2019 2:15:19 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 16062 (GAC) on 2019-08-10 and after.
     5 [8/10/2019 2:15:20 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 61776 (PASNUS) on 2019-08-10 and after.
     6 [8/10/2019 2:21:21 AM] [WARNG] Time discontinuity detected. Service 69101 (GOLTVEH) SH012857740000 (entry 43) ends at 2019-08-12 03:00:00Z, EP014682121186 (entry 44) starts at 2019-08-12 00:00:00Z. No further discontinuities on GOLTVEH will be reported for the date 2019-08-12.
     7 [8/10/2019 2:48:12 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
     8 [8/11/2019 2:15:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 79607 (UFEST) on 2019-08-11 and after.
     9 [8/11/2019 2:26:14 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    10 [8/12/2019 2:15:15 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 96635 (ESPCE8H) on 2019-08-12 and after.
    11 [8/12/2019 2:25:50 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    12 [8/13/2019 2:15:09 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 89542 (BBCWDNA) on 2019-08-13 and after.
    13 [8/13/2019 2:15:20 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 83075 (MPLEXHD) on 2019-08-13 and after.
    14 [8/13/2019 2:37:22 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    15 [8/13/2019 4:25:05 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 89542 (BBCWDNA) on 2019-08-13 and after.
    16 [8/13/2019 4:25:08 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 83075 (MPLEXHD) on 2019-08-13 and after.
    17 [8/13/2019 4:34:41 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    18 [8/14/2019 2:15:18 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 76378 (P12ORHD) on 2019-08-14 and after.
    19 [8/14/2019 2:26:01 AM] [WARNG] The imported MXF file contained a WARNING in its status field.

===== QUERY INFORMATION (Predefined) ===========================
Logs used:		trace.log ONLY
Search String:		[WARNG]
Date Range:		07/28/2019 thru 08/14/2019 (18 days)
Total results found:	19
Query time:		06 seconds
It's been my experience that these are caused by an inability to retrieve future information for particular channels. It's not detrimental and usually clears itself within a few days. It's the same with the time discontinuity.

In your case it appears that this is occurring on different channels... If it was the same channel every day, it might be worth looking into further.

Considering you have 4,727 "skipped matching" entries in only 18 days... I'll leave that to garyan2.

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.4 (64 bit)
Report Created on 08/14/2019 at 06:59:03
================================================================
     1 [7/28/2019 2:25:59 AM] [ INFO] Skipped matching ESPNDHD to channel 678 due to channel already having an assigned listing.
     2 [7/28/2019 2:25:59 AM] [ INFO] Skipped matching FXDEPHD to channel 679 due to channel already having an assigned listing.
     3 [7/28/2019 2:25:59 AM] [ INFO] Skipped matching HDM2DM to channel 701 due to channel already having an assigned listing.
	.
	[Truncated]
	.
  4725 [8/13/2019 2:37:21 AM] [ INFO] Skipped matching KTLADT3 to channel 5.3 due to channel already having an assigned listing.
  4726 [8/13/2019 2:37:21 AM] [ INFO] Skipped matching KNBCDT to channel 1004 due to channel already having an assigned listing.
  4727 [8/13/2019 2:37:21 AM] [ INFO] Skipped matching KNBCDT2 to channel 1003 due to channel already having an assigned listing.

===== QUERY INFORMATION (Custom) ===============================
Logs used:		trace.log ONLY
Search String:		Skipped matching
Date Range:		07/28/2019 thru 08/14/2019 (18 days)
Total results found:	4727
Query time:		05 seconds

Post Reply