Guide not updating. EPG123 error

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
dlitwin

Posts: 3
Joined: Thu Apr 10, 2014 10:01 pm
Location:

HTPC Specs: Show details

Guide not updating. EPG123 error

#1

Post by dlitwin » Tue Oct 01, 2019 2:02 am

Guide has been messed up in MC for couple months. Always get the red X on the guide icon in WMC.
I had cleared epg123 cache and also updated to latest version.

still same issues
Also deleted and reran the task setup.

Output of some of the trace file:

Exiting getAllSeriesImages(). SUCCESS.<br/>
[9/30/2019 2:07:15 AM] [ INFO] Completed compiling keywords and keyword groups.<br/>
[9/30/2019 2:07:18 AM] [ INFO] Completed save of the MXF file to "C:\epg123\output\epg123.mxf".<br/>
[9/30/2019 2:07:18 AM] [ INFO] Completed save of image archive file to "C:\epg123\guideImages.xml".<br/>
[9/30/2019 2:07:20 AM] [ INFO] 3343 files deleted from the cache directory during cleanup.<br/>
[9/30/2019 2:07:20 AM] [ INFO] Downloaded and processed 91.138 MB of data from Schedules Direct.<br/>
[9/30/2019 2:07:20 AM] [ INFO] Generated .mxf file contains 623 services, 8247 series, 43477 programs, and 68264 people with 13520 image links.<br/>
[9/30/2019 2:07:20 AM] [ INFO] Completed EPG123 update execution. SUCCESS.<br/>
[9/30/2019 2:07:20 AM] [ INFO] epg123 update execution time was 00:07:19.7959725.<br/>
[9/30/2019 2:07:20 AM] ===============================================================================<br/>
[9/30/2019 2:07:20 AM] Beginning epg123 client execution. version 1.2.18.0<br/>
[9/30/2019 2:07:20 AM] ===============================================================================<br/>
[9/30/2019 2:07:20 AM] [ INFO] Beginning epg123 client execution. 2019-09-30 07:07:20Z<br/>
[9/30/2019 2:07:20 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False<br/>
[9/30/2019 2:07:21 AM] Entering importMxfFile() for file "c:\epg123\output\epg123.mxf"<br/>
[9/30/2019 2:07:21 AM] [ INFO] Error: The following error was encountered while processing the file. Aborting.<br/>
[9/30/2019 2:07:21 AM] [ INFO] RowSet::SetData failed (name=DeviceGroup DeviceGroupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 2:07:22 AM] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1<br/>
[9/30/2019 2:07:22 AM] Exiting importMxfFile(). FAILURE.<br/>
[9/30/2019 2:07:22 AM] [ERROR] Failed to import .mxf file. Exiting.<br/>
[9/30/2019 5:26:09 PM] ===============================================================================<br/>
[9/30/2019 5:26:09 PM] Activating the epg123 client GUI. version 1.2.18.0<br/>
[9/30/2019 5:26:09 PM] ===============================================================================<br/>
[9/30/2019 5:26:09 PM] [ INFO] Successfully queried the Task Scheduler for status. Could not start. Last Run 9/30/2019 2:00:00 AM; Exit: 0xFFFFFFFF<br/>
[9/30/2019 5:26:33 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:26:36 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:26:38 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:26:41 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:26:53 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:25 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:33 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:37 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:48 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:50 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:27:51 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:28:00 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:28:02 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:28:02 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:28:47 PM] [ERROR] Unhandled thread exception caught from epg123Client.exe. message: RowSet::SetData failed (name=MergedLineup MergedLineupI_StoredObjectIdKey, rowHandle = 1, accessorHandle = 1) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""<br/>
[9/30/2019 5:28:49 PM] [ERROR] Unhandled thread excep<br/>
[/size]</t>

User avatar
garyan2

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

HTPC Specs: Show details

#2

Post by garyan2 » Tue Oct 01, 2019 3:38 am

Your database is corrupted. Open the client and click the [Rebuild WMC Database] button.

This has been going on for months?
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

dlitwin

Posts: 3
Joined: Thu Apr 10, 2014 10:01 pm
Location:

HTPC Specs: Show details

#3

Post by dlitwin » Tue Oct 01, 2019 10:55 pm

yeah, family and job got in the way. i just tuned to the station channel and watched the news at the normal time. I know, lame. :)

User avatar
garyan2

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

HTPC Specs: Show details

#4

Post by garyan2 » Wed Oct 02, 2019 1:25 am

Understand... the rebuild should put you back in business though.
- Gary
Stomping out the Rovi disease, one media center at a time. http://epg123.garyan2.net

Jacksondorf

Posts: 11
Joined: Wed Jul 05, 2017 6:55 am
Location: Arizona

HTPC Specs: Show details

#5

Post by Jacksondorf » Mon Oct 14, 2019 7:34 pm

I had a similar issue.... I was pretty sure the database was corrupt, as the final transfer of data to WMC would fail around 16%. I was thinking that a database rebuild would fix it, but not positive. So... was looking for the exact function of the rebuild before I did it. Found this, and it resolved my queasyness. :-)

Cheers, Jack

Post Reply