Yellow ! icon

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
dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

Re: Yellow ! icon

#21

Post by dahef » Wed Jun 26, 2019 10:15 pm

garyan2 wrote:
Wed Jun 26, 2019 9:54 pm
No that will just remove that channel from download on your next update. Click the [View Log] button and look for [WARNG] entries to see what the warning is for.
The imported MXF file contained a warning in it's status field.

User avatar
garyan2

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

HTPC Specs: Show details

#22

Post by garyan2 » Wed Jun 26, 2019 10:23 pm

There should be at least 1 more [WARNG] entry during the download phase before the client import entries.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#23

Post by dahef » Wed Jun 26, 2019 10:47 pm

garyan2 wrote:
Wed Jun 26, 2019 10:23 pm
There should be at least 1 more [WARNG] entry during the download phase before the client import entries.
A couple of Errors during Activation config gui which I think were before I set up listings -
INFO SD responded with error code 4107-No lineups have been added to this account.
ERROR Failed to complete Exiting
ERROR Did not receive a response from SD for a client lineup listing

Then later during Beginning update execution 3 warnings
WARNING - Failed to purse the schedule MD5 return for stationId 105673
WARNING - Failed to purse the schedule MD5 return for stationId 103231
WARNING - Failed to purse the schedule MD5 return for stationId 104729

User avatar
garyan2

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

HTPC Specs: Show details

#24

Post by garyan2 » Wed Jun 26, 2019 10:50 pm

Okay, the warning is for those 3 stations we did not get any guide data. I believe there should have been more information to identify exactly what stations they are. If not, you can use the station ID and compare it to the station IDs of your lineups in the configuration GUI.

I would try again in about 12 hours (SD update runs are 2 times a day), or you could open a ticket with SD to investigate and correct.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#25

Post by dahef » Wed Jun 26, 2019 11:01 pm

garyan2 wrote:
Wed Jun 26, 2019 10:50 pm
Okay, the warning is for those 3 stations we did not get any guide data. I believe there should have been more information to identify exactly what stations they are. If not, you can use the station ID and compare it to the station IDs of your lineups in the configuration GUI.

I would try again in about 12 hours (SD update runs are 2 times a day), or you could open a ticket with SD to investigate and correct.
I did leave out the end of each
(LOOR1081)
(GOAC1085)
(LOOR1098)

What is it I would be trying again. Save/Execute ??

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#26

Post by dahef » Wed Jun 26, 2019 11:25 pm

dahef wrote:
Wed Jun 26, 2019 11:01 pm
garyan2 wrote:
Wed Jun 26, 2019 10:50 pm
Okay, the warning is for those 3 stations we did not get any guide data. I believe there should have been more information to identify exactly what stations they are. If not, you can use the station ID and compare it to the station IDs of your lineups in the configuration GUI.

I would try again in about 12 hours (SD update runs are 2 times a day), or you could open a ticket with SD to investigate and correct.
I did leave out the end of each
(LOOR1081)
(GOAC1085)
(LOOR1098)

What is it I would be trying again. Save/Execute ??
I did find the channels in the config and unchecked them and did a Save/Execute. I then downloaded latest guide listings. Still Yellow. Perhaps I'm on the wrong track.

stuartm

Posts: 360
Joined: Mon Nov 05, 2012 8:05 pm
Location: Longmont, CO

HTPC Specs: Show details

#27

Post by stuartm » Wed Jun 26, 2019 11:31 pm

On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#28

Post by dahef » Wed Jun 26, 2019 11:37 pm

stuartm wrote:
Wed Jun 26, 2019 11:31 pm
On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.
I was hoping that unchecking them and reexecute and download would fix the trouble icon. Perhaps the twice a day update Garyan refers to will fix that,, or unless there is something I need to clear?

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#29

Post by dahef » Wed Jun 26, 2019 11:44 pm

dahef wrote:
Wed Jun 26, 2019 11:25 pm
dahef wrote:
Wed Jun 26, 2019 11:01 pm
garyan2 wrote:
Wed Jun 26, 2019 10:50 pm
Okay, the warning is for those 3 stations we did not get any guide data. I believe there should have been more information to identify exactly what stations they are. If not, you can use the station ID and compare it to the station IDs of your lineups in the configuration GUI.

I would try again in about 12 hours (SD update runs are 2 times a day), or you could open a ticket with SD to investigate and correct.
I did leave out the end of each
(LOOR1081)
(GOAC1085)
(LOOR1098)

What is it I would be trying again. Save/Execute ??
I did find the channels in the config and unchecked them and did a Save/Execute. I then downloaded latest guide listings. Still Yellow. Perhaps I'm on the wrong track.
I did get another warning on my last execute
Program SH03250717000 is missing required content.
Did not cache due to missing Md5 hash.

Same warning for EP002910440108

stuartm

Posts: 360
Joined: Mon Nov 05, 2012 8:05 pm
Location: Longmont, CO

HTPC Specs: Show details

#30

Post by stuartm » Thu Jun 27, 2019 12:00 am

dahef wrote:
Wed Jun 26, 2019 11:37 pm
stuartm wrote:
Wed Jun 26, 2019 11:31 pm
On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.
I was hoping that unchecking them and reexecute and download would fix the trouble icon. Perhaps the twice a day update Garyan refers to will fix that,, or unless there is something I need to clear?
I am not sure but I think you need to exit WMC and restart it for the Icon to change. Did you do that after you had a clean save&execute with no further warnings?
I might be wrong here Gary is very clever and maybe the icon will update on the fly. :)

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#31

Post by dahef » Thu Jun 27, 2019 12:08 am

stuartm wrote:
Thu Jun 27, 2019 12:00 am
dahef wrote:
Wed Jun 26, 2019 11:37 pm
stuartm wrote:
Wed Jun 26, 2019 11:31 pm
On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.
I was hoping that unchecking them and reexecute and download would fix the trouble icon. Perhaps the twice a day update Garyan refers to will fix that,, or unless there is something I need to clear?
I am not sure but I think you need to exit WMC and restart it for the Icon to change. Did you do that after you had a clean save&execute with no further warnings?
I might be wrong here Gary is very clever and maybe the icon will update on the fly. :)
I close WMC then I reopen afterwards.

User avatar
garyan2

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

HTPC Specs: Show details

#32

Post by garyan2 » Thu Jun 27, 2019 12:33 am

stuartm wrote:
Wed Jun 26, 2019 11:31 pm
On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.
SD contacted me about this a couple days ago. He talked with the upstream (Gracenote) and they said they have no intention of getting guide data for those stations anymore. SD did offer to populate the guide for those channels with 1-hour blocks of "To Be Announced" or something to that effect. I actually responded that from a WMC persepective, it would be best to have it empty, but I didn't think of the impact on EPG123.

Does anyone have a preference of what the guide should look like for these local/community channels that have no guide data? Just blocks of time that say "No Data Available."? Comments....
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
garyan2

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

HTPC Specs: Show details

#33

Post by garyan2 » Thu Jun 27, 2019 12:35 am

stuartm wrote:
Thu Jun 27, 2019 12:00 am
I might be wrong here Gary is very clever and maybe the icon will update on the fly. :)
I never found a way to do it on the fly. I can't remember if you need to fully exit, or just change screens and then go back to the home screen.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

dahef

Posts: 67
Joined: Mon Mar 14, 2016 7:11 pm
Location:

HTPC Specs: Show details

#34

Post by dahef » Thu Jun 27, 2019 12:48 am

garyan2 wrote:
Thu Jun 27, 2019 12:33 am
stuartm wrote:
Wed Jun 26, 2019 11:31 pm
On my lineup LOOR and GOAC are Local Origination and Government Access channels. Typically carrying things like city council meetings, and local programming from the cable co .. I would not be surprised if there is no data supplied to SD for those channels. I am getting nightly complaints about those in my lineup as well but am just ignoring the warning.
SD contacted me about this a couple days ago. He talked with the upstream (Gracenote) and they said they have no intention of getting guide data for those stations anymore. SD did offer to populate the guide for those channels with 1-hour blocks of "To Be Announced" or something to that effect. I actually responded that from a WMC persepective, it would be best to have it empty, but I didn't think of the impact on EPG123.

Does anyone have a preference of what the guide should look like for these local/community channels that have no guide data? Just blocks of time that say "No Data Available."? Comments....
With me any old blurb would do. Would I have to wait for this to happen before the yellow goes to green?

stuartm

Posts: 360
Joined: Mon Nov 05, 2012 8:05 pm
Location: Longmont, CO

HTPC Specs: Show details

#35

Post by stuartm » Thu Jun 27, 2019 12:51 am

I think "No Data Available" blocks would be best. "To Be Announced" might lead people to expect that it will eventually be filled in.

User avatar
garyan2

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

HTPC Specs: Show details

#36

Post by garyan2 » Thu Jun 27, 2019 12:57 am

stuartm wrote:I think "No Data Available" blocks would be best. "To Be Announced" might lead people to expect that it will eventually be filled in.
That was my sentiment as well.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

sorahl

Posts: 24
Joined: Thu Oct 23, 2014 10:59 am
Location:

HTPC Specs: Show details

#37

Post by sorahl » Thu Jun 27, 2019 3:27 am

Gary,
can you take a look at my trace.log and see why i've had a yellow icon for atleast a week (it seems)? The only thing I find is this
[6/26/2019 12:35:27 AM] [WARNG] The imported MXF file contained a WARNING in its status field.

Thanks..
John
Attachments
trace.zip
(42.58 KiB) Downloaded 6 times

User avatar
garyan2

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

HTPC Specs: Show details

#38

Post by garyan2 » Thu Jun 27, 2019 3:36 am

sorahl wrote:
Thu Jun 27, 2019 3:27 am
Gary,
can you take a look at my trace.log and see why i've had a yellow icon for atleast a week (it seems)? The only thing I find is this
[6/26/2019 12:35:27 AM] [WARNG] The imported MXF file contained a WARNING in its status field.

Thanks..
John
There was no guide data for the below stations:

Code: Select all

[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-26 and after.
[6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-26 and after.
They are your local "Public, Educational, Government" stations. There is a discussion I started on this thread to talk about how the future may look for these community stations that do not and/or will not have guide data in the future.

If you want to get rid of the warnings, you would have to remove those stations from the downloads.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

User avatar
StinkyImp

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

HTPC Specs: Show details

#39

Post by StinkyImp » Thu Jun 27, 2019 1:24 pm

sorahl wrote:
Thu Jun 27, 2019 3:27 am
Gary,
can you take a look at my trace.log and see why i've had a yellow icon for atleast a week (it seems)? The only thing I find is this
[6/26/2019 12:35:27 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
Here's a concise listing of all the "Warnings" in your trace.log file:

Code: Select all

EPG123 Log Parser (and Report Generator) - v 1.7.3 (64 bit)
Report Created on 06/27/2019 at 06:20:22
================================================================
     1 [6/16/2019 12:35:25 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
     2 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-17 and after.
     3 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-17 and after.
     4 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-17 and after.
     5 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-17 and after.
     6 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-17 and after.
     7 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-17 and after.
     8 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-17 and after.
     9 [6/17/2019 12:00:22 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-17 and after.
    10 [6/17/2019 12:02:05 AM] [WARNG] Program EP022705780090 is missing required content.
    11 [6/17/2019 12:02:05 AM] [WARNG] Did not cache program EP022705780090 due to missing Md5 hash.
    12 [6/17/2019 12:02:05 AM] [WARNG] Program EP018723670097 is missing required content.
    13 [6/17/2019 12:02:05 AM] [WARNG] Did not cache program EP018723670097 due to missing Md5 hash.
    14 [6/17/2019 12:02:06 AM] [WARNG] Program EP015976280116 is missing required content.
    15 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP015976280116 due to missing Md5 hash.
    16 [6/17/2019 12:02:06 AM] [WARNG] Program EP032515590001 is missing required content.
    17 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP032515590001 due to missing Md5 hash.
    18 [6/17/2019 12:02:06 AM] [WARNG] Program EP029804450038 is missing required content.
    19 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP029804450038 due to missing Md5 hash.
    20 [6/17/2019 12:02:06 AM] [WARNG] Program EP027379100445 is missing required content.
    21 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027379100445 due to missing Md5 hash.
    22 [6/17/2019 12:02:06 AM] [WARNG] Program EP027379100446 is missing required content.
    23 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027379100446 due to missing Md5 hash.
    24 [6/17/2019 12:02:06 AM] [WARNG] Program EP012160700525 is missing required content.
    25 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP012160700525 due to missing Md5 hash.
    26 [6/17/2019 12:02:06 AM] [WARNG] Program EP007570040256 is missing required content.
    27 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP007570040256 due to missing Md5 hash.
    28 [6/17/2019 12:02:06 AM] [WARNG] Program EP030576840008 is missing required content.
    29 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP030576840008 due to missing Md5 hash.
    30 [6/17/2019 12:02:06 AM] [WARNG] Program EP028989240060 is missing required content.
    31 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP028989240060 due to missing Md5 hash.
    32 [6/17/2019 12:02:06 AM] [WARNG] Program EP025281610317 is missing required content.
    33 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP025281610317 due to missing Md5 hash.
    34 [6/17/2019 12:02:06 AM] [WARNG] Program EP027862300454 is missing required content.
    35 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027862300454 due to missing Md5 hash.
    36 [6/17/2019 12:02:06 AM] [WARNG] Program EP027619980476 is missing required content.
    37 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027619980476 due to missing Md5 hash.
    38 [6/17/2019 12:02:06 AM] [WARNG] Program EP030474760195 is missing required content.
    39 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP030474760195 due to missing Md5 hash.
    40 [6/17/2019 12:02:06 AM] [WARNG] Program EP011588690149 is missing required content.
    41 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP011588690149 due to missing Md5 hash.
    42 [6/17/2019 12:02:06 AM] [WARNG] Program EP027723480459 is missing required content.
    43 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027723480459 due to missing Md5 hash.
    44 [6/17/2019 12:02:06 AM] [WARNG] Program EP023775430077 is missing required content.
    45 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP023775430077 due to missing Md5 hash.
    46 [6/17/2019 12:02:06 AM] [WARNG] Program EP025281610318 is missing required content.
    47 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP025281610318 due to missing Md5 hash.
    48 [6/17/2019 12:02:06 AM] [WARNG] Program EP027862300455 is missing required content.
    49 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027862300455 due to missing Md5 hash.
    50 [6/17/2019 12:02:06 AM] [WARNG] Program EP027619980477 is missing required content.
    51 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027619980477 due to missing Md5 hash.
    52 [6/17/2019 12:02:06 AM] [WARNG] Program EP011588690150 is missing required content.
    53 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP011588690150 due to missing Md5 hash.
    54 [6/17/2019 12:02:06 AM] [WARNG] Program EP027723480460 is missing required content.
    55 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP027723480460 due to missing Md5 hash.
    56 [6/17/2019 12:02:06 AM] [WARNG] Program EP016483270997 is missing required content.
    57 [6/17/2019 12:02:06 AM] [WARNG] Did not cache program EP016483270997 due to missing Md5 hash.
    58 [6/17/2019 12:04:54 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    59 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-18 and after.
    60 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-18 and after.
    61 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-18 and after.
    62 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-18 and after.
    63 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-18 and after.
    64 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-18 and after.
    65 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-18 and after.
    66 [6/18/2019 12:00:28 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-18 and after.
    67 [6/18/2019 2:20:39 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    68 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-19 and after.
    69 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-19 and after.
    70 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-19 and after.
    71 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-19 and after.
    72 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-19 and after.
    73 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-19 and after.
    74 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-19 and after.
    75 [6/19/2019 12:00:24 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-19 and after.
    76 [6/19/2019 12:35:17 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    77 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-20 and after.
    78 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-20 and after.
    79 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-20 and after.
    80 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-20 and after.
    81 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-20 and after.
    82 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-20 and after.
    83 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-20 and after.
    84 [6/20/2019 12:00:25 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-20 and after.
    85 [6/20/2019 12:35:20 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    86 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-21 and after.
    87 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-21 and after.
    88 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-21 and after.
    89 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-21 and after.
    90 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-21 and after.
    91 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-21 and after.
    92 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-21 and after.
    93 [6/21/2019 12:00:26 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-21 and after.
    94 [6/21/2019 12:02:15 AM] [WARNG] Program EP011602731452 is missing required content.
    95 [6/21/2019 12:02:15 AM] [WARNG] Did not cache program EP011602731452 due to missing Md5 hash.
    96 [6/21/2019 12:02:16 AM] [WARNG] Program EP004883680186 is missing required content.
    97 [6/21/2019 12:02:16 AM] [WARNG] Did not cache program EP004883680186 due to missing Md5 hash.
    98 [6/21/2019 12:35:25 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
    99 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-22 and after.
   100 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-22 and after.
   101 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-22 and after.
   102 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-22 and after.
   103 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-22 and after.
   104 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-22 and after.
   105 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-22 and after.
   106 [6/22/2019 12:00:38 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-22 and after.
   107 [6/22/2019 12:35:25 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
   108 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-23 and after.
   109 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-23 and after.
   110 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-23 and after.
   111 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-23 and after.
   112 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-23 and after.
   113 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-23 and after.
   114 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-23 and after.
   115 [6/23/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-23 and after.
   116 [6/23/2019 1:05:27 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
   117 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-24 and after.
   118 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-24 and after.
   119 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-24 and after.
   120 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-24 and after.
   121 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-24 and after.
   122 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-24 and after.
   123 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-24 and after.
   124 [6/24/2019 12:00:34 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-24 and after.
   125 [6/24/2019 12:05:29 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
   126 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-24 and after.
   127 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-24 and after.
   128 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-24 and after.
   129 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-24 and after.
   130 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-24 and after.
   131 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-24 and after.
   132 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-24 and after.
   133 [6/24/2019 5:11:50 PM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-24 and after.
   134 [6/24/2019 6:03:16 PM] [WARNG] The imported MXF file contained a WARNING in its status field.
   135 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-25 and after.
   136 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-25 and after.
   137 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-25 and after.
   138 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-25 and after.
   139 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-25 and after.
   140 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-25 and after.
   141 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-25 and after.
   142 [6/25/2019 12:00:32 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-25 and after.
   143 [6/25/2019 12:35:09 AM] [WARNG] The imported MXF file contained a WARNING in its status field.
   144 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23908 (PEG032) on 2019-06-26 and after.
   145 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23909 (PEG033) on 2019-06-26 and after.
   146 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23910 (PEG034) on 2019-06-26 and after.
   147 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23911 (PEG035) on 2019-06-26 and after.
   148 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23912 (PEG036) on 2019-06-26 and after.
   149 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23913 (PEG037) on 2019-06-26 and after.
   150 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23914 (PEG038) on 2019-06-26 and after.
   151 [6/26/2019 12:00:33 AM] [WARNG] Failed to parse the schedule Md5 return for stationId 23915 (PEG039) on 2019-06-26 and after.
   152 [6/26/2019 12:35:27 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:		06/16/2019 thru 06/26/2019 (11 days)
Total results found:	152
Query time:		02 seconds

===== GENERAL INFORMATION ======================================
Log Path:		C:\epg123\
Logfile timespan:	6/16/2019 thru 6/26/2019 (11 days)
Total lines processed:	3758
Good news! There weren't any errors found.

sorahl

Posts: 24
Joined: Thu Oct 23, 2014 10:59 am
Location:

HTPC Specs: Show details

#40

Post by sorahl » Thu Jun 27, 2019 4:13 pm

thanks to both of you. i have removed the PEG channels. we never watch them anyway. i'll see how it goes

CHeers,

John

Post Reply