v1.1.2 Release

[garyan2]

I know, right!?! I pushed out a quick release to address an error in my code. I tried to be clever and do in 2 lines of code, what should have been done properly in 3 lines, not thinking about the impact to international users. The fix was for sorting of the listviews and channel/subchannel numbers. That is the only thing different between v1.1.1 and v1.1.2. So if you don't have any problems now, no need to rush for the newer version.

http://epg123.garyan2.net/

[kd6icz]

Lol! I'm moving servers next week so I'm holding out until then to upgrade to work out the kinks.

Sent from my XT1650 using Tapatalk

[Sammy2]

I'm still on 1.0.2.. It works and I have other projects on my plate. I suppose I could roll over to 1.1.2 but want to test it out on my other PC first. That PC isn't really used for WMC at all but is Win7x64Pro. It has the old MS/Rovi/TiVo guide still. Is the procedure the same going from that to epg123 v1.1.2 as going from epg123 v1.0.2 or is there a different procedure? I need to make sure when I make the change on the daily driver there's no issues whatsoever. We have nearly 100 series scheduled and a lot of recorded content that my wife watches every single day. Loosing either one will mean I need to take up residence in the Igloo with the dogs and it is cold and raining out there!

[kd6icz]

I'm still currently on 1.0.2 too. It works well. But I'm upgrading the server this weekend to something with lots and lots of cores. Ok.... 24 cores. For Plex. But the server also runs WMC so it gets upgraded too. Plus I can set up clients for all my mini HTPC's I have around the house.

Sent from my XT1650 using Tapatalk

[rimmel]

I just ran V1.1.2 and everything completed but I have some comments and questions.

1. Thanks for making the change to keep "Automatically import guide data into WMC" and "Automatically match stations to channels" checked on subsequent runs.

2. I got the following huge error message in the trace log. I have never seen this before. No abnormal stuff in the event log either.

[ERROR] WritingEventLog Failed with System.ArgumentException: Log entry string is too long. A string written to the event log cannot exceed 32766 characters.
at System.Diagnostics.EventLogInternal.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
at System.Diagnostics.EventLogInternal.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at epg123.EventLogger.InsertEventLog(EventLogEntryType evtLogType, String strMsg)

3. You wrote the following for V1.1.1: "Updated column sorters to treat channel numbers as Channel.Subchannel instead of decimal" I saw no difference in channel column sorting in V1.1.1. However, in V1.1.2 the column sorting is confusing to me. Are you sorting by something you call the "Subchannel" which does not actually appear in the column? For instance, when I attempt to sort by channel number I get the following sequence 1, 10, 102, 103, 104, 105, 106, 107, 11, 110, 111, 113, 114, 118, 12, 120, 121 ... What's going on here?

[garyan2]

1. Thanks for making the change to keep "Automatically import guide data into WMC" and "Automatically match stations to channels" checked on subsequent runs.

You're welcome. Just to let you know, any scheduled task you create will override your options.

2. I got the following huge error message in the trace log. I have never seen this before. No abnormal stuff in the event log either.

[ERROR] WritingEventLog Failed with System.ArgumentException: Log entry string is too long. A string written to the event log cannot exceed 32766 characters.
at System.Diagnostics.EventLogInternal.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
at System.Diagnostics.EventLogInternal.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at epg123.EventLogger.InsertEventLog(EventLogEntryType evtLogType, String strMsg)

Yah, found out I was logging Md5 mismatches in the event log and there are quite a number of them out there right now (I'll have to verify). Working on it.

3. You wrote the following for V1.1.1: "Updated column sorters to treat channel numbers as Channel.Subchannel instead of decimal" I saw no difference in channel column sorting in V1.1.1. However, in V1.1.2 the column sorting is confusing to me. Are you sorting by something you call the "Subchannel" which does not actually appear in the column? For instance, when I attempt to sort by channel number I get the following sequence 1, 10, 102, 103, 104, 105, 106, 107, 11, 110, 111, 113, 114, 118, 12, 120, 121 ... What's going on here?

What's going on is I really need to get some sleep. I believe the problem is just in the epg123.exe, not the client. I'll confirm that as well.

[garyan2]

Though this version makes the GUIs functional for international users, the actual sorting is now broken. That has been corrected in the code and will be in the next release. Recommend using v1.1.1 if it works for your system configuration.

[jkr4m3r]

I have 1.1.0 installed, do I simply overwrite the files from the 112 7z file?

[garyan2]

I have 1.1.0 installed, do I simply overwrite the files from the 112 7z file?

That's all you need to do, though I would just go to 1.1.1, not 1.1.2. I broke the column sorting in 1.1.2.

[jkr4m3r]

I have 1.1.0 installed, do I simply overwrite the files from the 112 7z file?

That's all you need to do, though I would just go to 1.1.1, not 1.1.2. I broke the column sorting in 1.1.2.

Beat ya to it after I red the bold red type. All is well, thank you!

[neptunepic]

Hi, channel numbers do not sort in correct numeric order, see attached.

[neptunepic]

Hi again, I'm also getting a lot of warnings in the event viewer. See below.

3:00:18 AM - The MD5 hash of Program EP001887105871 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP019952930308 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP000006529177 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP025695370009 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP021854370016 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP017729580095 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP024818880017 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH000167470000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP017729500096 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH024336590000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP011583610190 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH024336450000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH015388740000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH011748390000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH015731120000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH026311380000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH020941260000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP013099671664 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP013099671665 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP000011894405 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP005992702437 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP013099671666 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP001887075842 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH015223350000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP001887075844 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program SH013657560000 does not match the expected MD5 provided by the Service Schedule.
3:00:18 AM - The MD5 hash of Program EP013657560311 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP013657560312 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP024314420017 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP013657560322 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP024971070123 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP024971070124 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP014408400113 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program SH024839920000 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP014408400114 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP014408400115 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP005987610656 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program SH005455790000 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP019743070042 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP019218760055 does not match the expected MD5 provided by the Service Schedule.
3:00:19 AM - The MD5 hash of Program EP017396170089 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program SH011581190000 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program EP006228693366 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program SH019612840000 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program SH015872090000 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program EP010616541523 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program EP005544655290 does not match the expected MD5 provided by the Service Schedule.
3:00:20 AM - The MD5 hash of Program EP024316050005 does not match the expected MD5 provided by the Service Schedule.
3:00:21 AM - The MD5 hash of Program EP024316050003 does not match the expected MD5 provided by the Service Schedule.
3:00:21 AM - The MD5 hash of Program EP010616541521 does not match the expected MD5 provided by the Service Schedule.
3:00:21 AM - The MD5 hash of Program EP008378340061 does not match the expected MD5 provided by the Service Schedule.
3:00:21 AM - The MD5 hash of Program EP008378340062 does not match the expected MD5 provided by the Service Schedule.
3:00:22 AM - The MD5 hash of Program SH009248440000 does not match the expected MD5 provided by the Service Schedule.
3:00:22 AM - The MD5 hash of Program SH012801370000 does not match the expected MD5 provided by the Service Schedule.
3:00:22 AM - The MD5 hash of Program SP003471120000 does not match the expected MD5 provided by the Service Schedule.
3:00:22 AM - The MD5 hash of Program SP003471140000 does not match the expected MD5 provided by the Service Schedule.
3:00:22 AM - The MD5 hash of Program EP014328840091 does not match the expected MD5 provided by the Service Schedule.
3:00:23 AM - The MD5 hash of Program EP013323921012 does not match the expected MD5 provided by the Service Schedule.
3:00:23 AM - The MD5 hash of Program EP013323921013 does not match the expected MD5 provided by the Service Schedule.
3:00:23 AM - The MD5 hash of Program EP013323921014 does not match the expected MD5 provided by the Service Schedule.
3:00:23 AM - The MD5 hash of Program MV002185980000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP015979600521 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP015979600522 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP015979600523 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP015979600524 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH000777030000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH000672640000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP015683360029 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP023500650009 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH017011490000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH016415600000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SP003471070000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SP003471100000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH026064820000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SH026214670000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program SP003471230000 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP000215267258 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP000215267259 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP014651844913 does not match the expected MD5 provided by the Service Schedule.
3:00:24 AM - The MD5 hash of Program EP014651844934 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP025983280734 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP000215267257 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP005544655328 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP005544655361 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SH026158380000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP008965610691 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SP003632190000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP018448080046 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program EP008965610694 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SP003506730000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SP003507070000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SP003451770000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SP003451780000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SH012905770000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SH026286390000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SH025767940000 does not match the expected MD5 provided by the Service Schedule.
3:00:25 AM - The MD5 hash of Program SH026314140000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program EP022070900018 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH016566900000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH010835610000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH025381650000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH026162440000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH022117330000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH023188980000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH015103710000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program EP024439090004 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program EP025975000004 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program EP025975000005 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH012597270000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program SH008159770000 does not match the expected MD5 provided by the Service Schedule.
3:00:26 AM - The MD5 hash of Program EP014120730157 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP025526100004 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP014120730159 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP025526100008 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program SH012960890000 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970031 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970034 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970091 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970094 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970098 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015417210051 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970011 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970045 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970099 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970024 does not match the expected MD5 provided by the Service Schedule.
3:00:27 AM - The MD5 hash of Program EP015033970026 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP013916300021 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP010549430181 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP026144080001 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP026144080002 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP026288920003 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP014673830088 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP022130320011 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program SH026272750000 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP014673830089 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP022130320012 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program SH026293450000 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP022130320013 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP010699450008 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP015237480065 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP013602000040 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP013602000039 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP013602000038 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP013602000041 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP009618610283 does not match the expected MD5 provided by the Service Schedule.
3:00:28 AM - The MD5 hash of Program EP023617780020 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP026111880007 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP018739050153 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP026111880004 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP023975080032 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP023881180009 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP026100300001 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP005178512655 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP015577560060 does not match the expected MD5 provided by the Service Schedule.
3:00:29 AM - The MD5 hash of Program EP022373590555 does not match the expected MD5 provided by the Service Schedule.
3:00:30 AM - The MD5 hash of Program EP011092050005 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP017820660128 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP017820660131 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP009089410382 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP014328710197 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP015393540105 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP018375220155 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP017899670161 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP021963430066 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP020820940063 does not match the expected MD5 provided by the Service Schedule.
3:00:31 AM - The MD5 hash of Program EP020820940064 does not match the expected MD5 provided by the Service Schedule.
3:00:32 AM - The MD5 hash of Program EP020959710003 does not match the expected MD5 provided by the Service Schedule.
3:00:32 AM - The MD5 hash of Program EP020959710004 does not match the expected MD5 provided by the Service Schedule.
3:00:32 AM - The MD5 hash of Program EP020959710005 does not match the expected MD5 provided by the Service Schedule.
3:00:32 AM - The MD5 hash of Program EP023507480025 does not match the expected MD5 provided by the Service Schedule.
3:00:33 AM - The MD5 hash of Program EP024585350020 does not match the expected MD5 provided by the Service Schedule.
3:00:33 AM - The MD5 hash of Program SH026313680000 does not match the expected MD5 provided by the Service Schedule.
3:00:33 AM - The MD5 hash of Program SH026313720000 does not match the expected MD5 provided by the Service Schedule.
3:00:33 AM - The MD5 hash of Program SH020865430000 does not match the expected MD5 provided by the Service Schedule.
3:00:33 AM - The MD5 hash of Program EP016660830118 does not match the expected MD5 provided by the Service Schedule.
3:00:34 AM - The MD5 hash of Program SH016996050000 does not match the expected MD5 provided by the Service Schedule.
3:00:34 AM - The MD5 hash of Program EP000186930128 does not match the expected MD5 provided by the Service Schedule.
3:00:35 AM - The MD5 hash of Program EP000042172795 does not match the expected MD5 provided by the Service Schedule.
3:00:35 AM - The MD5 hash of Program EP009675940337 does not match the expected MD5 provided by the Service Schedule.
3:00:35 AM - The MD5 hash of Program EP025614740007 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program SH015471390000 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP026119510001 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP026119510002 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP013740110174 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP026119510003 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP014000660160 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP026027670005 does not match the expected MD5 provided by the Service Schedule.
3:00:36 AM - The MD5 hash of Program EP014000660164 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP015697660088 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP017713010043 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP024851610006 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP017713010044 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP015683360109 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP025860590003 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program EP013240020135 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program MV004791520000 does not match the expected MD5 provided by the Service Schedule.
3:00:37 AM - The MD5 hash of Program MV001498670000 does not match the expected MD5 provided by the Service Schedule.
3:00:38 AM - The MD5 hash of Program EP013623190074 does not match the expected MD5 provided by the Service Schedule.
3:00:40 AM - The MD5 hash of Program MV001161220000 does not match the expected MD5 provided by the Service Schedule.
3:00:40 AM - The MD5 hash of Program EP022544240035 does not match the expected MD5 provided by the Service Schedule.
3:00:40 AM - The MD5 hash of Program EP019534220067 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program SH012082720000 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program SH019534220000 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program SH017625240000 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP017123260295 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP025761330009 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program SH014122930000 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP025634050002 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP012792980017 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP012792980019 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP025761330010 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP004517020103 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP010591100079 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP015598770049 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP015598770047 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP025105560010 does not match the expected MD5 provided by the Service Schedule.
3:00:41 AM - The MD5 hash of Program EP015598770045 does not match the expected MD5 provided by the Service Schedule.
3:00:42 AM - The MD5 hash of Program EP023534900021 does not match the expected MD5 provided by the Service Schedule.
3:00:43 AM - The MD5 hash of Program EP017416530042 does not match the expected MD5 provided by the Service Schedule.
3:00:43 AM - The MD5 hash of Program EP002349780004 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program EP005537220417 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program EP015697930059 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program EP018772540099 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program EP023187490005 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program EP023187490006 does not match the expected MD5 provided by the Service Schedule.
3:00:44 AM - The MD5 hash of Program MV000872590000 does not match the expected MD5 provided by the Service Schedule.
3:00:45 AM - The MD5 hash of Program EP017024710060 does not match the expected MD5 provided by the Service Schedule.

[stuartm]

If you had read the posts just above yours you would have seen that both of these are known problems that Gary is working on.

[IT Troll]

Hi again, I'm also getting a lot of warnings in the event viewer. See below. <snip>

There is insufficient data to be certain, but I think you might be getting one or two MD5 mismatches.

[neptunepic]

Sorry guys, I didn't fully understand Gary's response earlier. Looking forward to the fixes.

[garyan2]

Fixes are available. v1.1.3 has been released.

[Sancho]

Fixes are available. v1.1.3 has been released.

Thanks for the quick fix, and for the "Operation Complete" pop-up when manually importing the MXF