Error: An item with the same key has already been added

[stuartm]

I have 3 systems running EPG123, 2 are relatively down level (1.1.19) and ran their updates fine last night although there were time discontinuity warnings. The system running the fairly new rev of EPG123 (1.3.5.30) failed with this error:

[5/28/2020 4:13:02 AM] Exiting buildLineupServices(). SUCCESS.
[5/28/2020 4:13:02 AM] Entering getAllScheduleEntryMd5s() for 16 days on 597 stations.
[5/28/2020 4:13:04 AM] [ INFO] Successfully retrieved Md5s for 312 station's daily schedules. (0:00:00:02.2932040 / 531.172 KB)
[5/28/2020 4:13:05 AM] [ERROR] Unhandled exception caught from epg123.exe. message: An item with the same key has already been added.

And then later imported the day old MXF.
All 3 systems are importing the exact same lineups and are using the same list of subscribed channels.
Id this some kind of problem on my end or is it a problem with SD data?

[garyan2]

Can't say I've ever seen that problem either. Could you send me your lineup and I'll check it out here. Based on that error, it looks like SD sent you the same station+day schedule twice.

[stuartm]

The lineups are these:
[5/28/2020 4:13:02 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-CO65363-X.
[5/28/2020 4:13:02 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-OTA-80503.

So I just did a save&execute and of course it ran fine with no errors. Must have been a temporary glitch in the SD data?

[garyan2]

Didn't have any issues with 1.3.7.30.
Downgraded to 1.3.5.30... still no issues.

If you do a [Save & Execute], and it works, then the problem was in the response from SD. If it still fails, try to clear the cache and do a [Save & Execute] again.

EDIT: I guess I should have read your entire message... went straight to testing it out. Yes, it looks like the problem would have been in the response from SD. This happens sometimes when they are in the process of updating their data on the AWS servers from the Gracenote servers. I've just never seen it present itself in this fashion. Usually it is an incorrect MD5 hash.

[glorp]

I had the same error sequence yesterday

Code: Select all

[5/28/2020 6:00:10 AM] [ INFO] Successfully retrieved the station mapping for lineup USA-WA63873-X.
[5/28/2020 6:00:11 AM] Exiting buildLineupServices(). SUCCESS.
[5/28/2020 6:00:11 AM] Entering getAllScheduleEntryMd5s() for 14 days on 601 stations.
[5/28/2020 6:00:16 AM] [ INFO] Successfully retrieved Md5s for 357 station's daily schedules. (0:00:00:05.2723388 /   532.233 KB)
[5/28/2020 6:00:16 AM] [ERROR] Unhandled exception caught from epg123.exe. message: An item with the same key has already been added.

[cbarbie]

I received the same error today. Multiple updates, hours apart and the error continues.

[garyan2]

I checked this out for lineup USA-WA63873-X. The problem is the Tennis Channel (TENNIS) has the same md5 hash for 2/23 and 2/24 which is not possible. I don't have a catch in there or method to handle an error like this in the download.

SD updates their servers twice a day, so it will probably clear itself whenever that happens. I'll take a look to see what I can do and report on errors like this.

[garyan2]

New version release to handle duplicate Md5 schedule entries downloaded from Schedules Direct plus a couple other things.