1.7.1.12 Failing to update WMC

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
gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

1.7.1.12 Failing to update WMC

#1

Post by gsr » Sat Sep 17, 2022 10:17 pm

I happened to notice that my guide update status was showing in red yesterday. I upgraded to the latest version of EPG123, but the guide update that ran this morning failed to successfully complete the client execution portion of the update. Any suggestions on how to get my system back to a happy state would be appreciated. The following is an excerpt from the trace log file showing the error messages:

Code: Select all

[9/17/2022 2:02:16 AM] [ INFO] Completed compiling keywords and keyword groups.
[9/17/2022 2:02:21 AM] [ INFO] Completed save of the MXF file to "C:\epg123\output\epg123.mxf".
[9/17/2022 2:02:21 AM] [ INFO] 6471 entries deleted from the cache file during cleanup.
[9/17/2022 2:02:25 AM] [ INFO] Generated .mxf file contains 803 services, 11855 series, 5896 seasons, 62117 programs, 328625 schedule entries, and 85773 people with 10802 image links.
[9/17/2022 2:02:25 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[9/17/2022 2:02:25 AM] [ INFO] epg123 update execution time was 00:02:24.8802867.
[9/17/2022 2:02:25 AM] ===============================================================================
[9/17/2022 2:02:25 AM]  Beginning epg123 client execution. version 1.7.1.12
[9/17/2022 2:02:25 AM] ===============================================================================
[9/17/2022 2:02:25 AM] *** Windows 7 Ultimate, 64-bit [Version: 6.1.7601.0] ***
[9/17/2022 2:02:25 AM] *** Windows Media Center [Version: 6.1.7600.16385] is installed. ***
[9/17/2022 2:02:25 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False , NoGC: False , NoVerify: False , Verbose: False
[9/17/2022 2:02:26 AM] Entering PerformGarbageCleanup().
[9/17/2022 2:11:06 AM] [ INFO] Unhandled Exception: System.InvalidOperationException: CollectionInfo CollectionInfoI_StoredObjectIdKey: InsertRow() failed (attempt 0 of 10) for (1, 997DD8020000140000000000002E000000) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.Rowset.InsertRow(Byte[] data)
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.OleDB.StoredObjectsEnumerator.Insert(Object obj)
[9/17/2022 2:11:06 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.CollectionEnumerator.Insert(Byte status, CollectionInfo collectionInfo)
[9/17/2022 2:11:06 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.PopulateCollectionTable()
[9/17/2022 2:11:06 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.PerformCollection()
[9/17/2022 2:11:06 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.Collect(String fileName, Boolean disableThrottle, Boolean createDbBackups, TraceOp traceLevel)
[9/17/2022 2:11:06 AM] [ INFO]    at Updater.Run()
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMain(HINSTANCE__* hInst, HINSTANCE__* hInstPrev, UInt16* pwzCmdLine, Int32 nCmdShow)
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMainCRTStartup()
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMainStub()
[9/17/2022 2:11:06 AM] [ INFO] Unhandled Exception: System.InvalidOperationException: Error getting IDBCreateCommand - HR = 0x0
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteErr.LogAndThrowException(Int32 hr, String msg, Object[] args)
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteCommand.CreateCommand(IUnknown** ppunk)
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteCommand.InitNativeCommand()
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteSession.ExecuteSql(String sql)
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteSession.DeleteCollectionInfoTable()
[9/17/2022 2:11:06 AM] [ INFO]    at MediaCenter.Store.OleDB.ObjectStore.DeleteCollectionInfoTable()
[9/17/2022 2:11:06 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.Collect(String fileName, Boolean disableThrottle, Boolean createDbBackups, TraceOp traceLevel)
[9/17/2022 2:11:06 AM] [ INFO]    at Updater.Run()
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMain(HINSTANCE__* hInst, HINSTANCE__* hInstPrev, UInt16* pwzCmdLine, Int32 nCmdShow)
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMainCRTStartup()
[9/17/2022 2:11:06 AM] [ INFO]    at wWinMainStub()
[9/17/2022 2:11:06 AM] [ERROR] Error using mcupdate.exe to perform database garbage cleanup. Exit code: -532459699
[9/17/2022 2:11:06 AM] Exiting PerformGarbageCleanup(). FAILURE.
[9/17/2022 2:11:06 AM] Entering ImportMxfFile() for file "c:\epg123\output\epg123.mxf".
[9/17/2022 2:11:07 AM] [ INFO] Error: The following error was encountered while processing the file. Aborting.
[9/17/2022 2:11:07 AM] [ INFO] GuideImage: InsertRow() failed (attempt 0 of 10) for (1, 17D4C00500002D00000000000100000015B805000000050000000000000000005000000068007400740070003A002F002F00470045004F00460046005300450052005600450052003A0039003000300039002F006C006F0067006F0073002F0057005500540046005F0064002E0070006E00670000006E00670000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A042381C00000000) - HR = 0x80004005
[9/17/2022 2:11:07 AM] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[9/17/2022 2:11:07 AM] Exiting ImportMxfFile(). FAILURE.
[9/17/2022 2:11:07 AM] [ERROR] Failed to import .mxf file. Exiting.
[9/17/2022 2:11:07 AM] [ INFO] MXF file was created on 9/17/2022 2:00:00 AM
[9/17/2022 2:11:07 AM] [ INFO] Completed EPG123 client execution.
[9/17/2022 2:11:07 AM] [ INFO] EPG123 client execution time was 00:08:41.7358415.

Space

Posts: 2587
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#2

Post by Space » Sat Sep 17, 2022 11:25 pm

Looks like your WMC database is corrupted, you most likely have to use the [Rebuild WMC Database] button in the EPG123 client.

You can wait for Gary to respond to see if he has any other ideas, but due to the failure being with the garbage cleanup, I doubt there is anything else that can be done.

After the rebuild, your program guide will be empty, so you will have to use the EPG123 client [Manual import] button to import the MXF file that was created from your above run of EPG123 (or you can just create a new MXF file and have it imported by using the right-click menu "Update guide now" option on the EPG123 systray icon).

Note that most likely the lineup/Series/favorite lineups will be restored from 5 days ago, since that is most likely when the last successful backup was taken. Note also that "you will lose your recording history (not the recordings), but everything else should be good." This means that all your existing recording should still be there, but you may see some Series try to re-record episodes that you have already recorded in the past (particularly those set to "New & Rerun"), so you may want to look at the upcoming list of scheduled recordings and tell it to not record any that you don't need (although if a Series is set to "New"-only then you only have to do that for upcoming recordings that are within the next 7 days.)

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#3

Post by gsr » Sun Sep 18, 2022 12:53 pm

Thanks for the response and it's along the lines of what I was expecting, though I hope Gary will chime in with another option. Losing my recording history wouldn't be a huge problem as most of my recordings are set up to record "New" episodes only. The update for this morning was a bit different (I'm including 2 snippets from the log), and my list of upcoming scheduled recordings was updated, but is still showing as red in WMC presumably because the garbage cleanup failed.

Code: Select all

[9/18/2022 2:03:02 AM] ===============================================================================
[9/18/2022 2:03:02 AM]  Beginning epg123 client execution. version 1.7.1.12
[9/18/2022 2:03:02 AM] ===============================================================================
[9/18/2022 2:03:02 AM] *** Windows 7 Ultimate, 64-bit [Version: 6.1.7601.0] ***
[9/18/2022 2:03:02 AM] *** Windows Media Center [Version: 6.1.7600.16385] is installed. ***
[9/18/2022 2:03:02 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False , NoGC: False , NoVerify: False , Verbose: False
[9/18/2022 2:03:03 AM] Entering PerformGarbageCleanup().
[9/18/2022 2:04:38 AM] [ INFO] Unhandled Exception: System.Runtime.InteropServices.ExternalException: StoredObjectsEnumerator.OpenRowset: Couldnt Open Rowset Error=0x80040e37, Message=Error in Rowset::OpenRowset(CollectionInfo, I_StoredObjectIdKey) - HR = 0x80040e37, 0, 0, 0, "CollectionInfo", "", ""
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.OleDB.StoredObjectsEnumerator.OpenRowset(StoredObjectKey key, String sqlQuery)
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.OleDB.StoredObjectsEnumerator.EnsureRowsetIsOpen()
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.OleDB.StoredObjectsEnumerator.InternalSeek(StoredObjectKey key, SeekType seekType)
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.OleDB.StoredObjectsEnumerator.Seek(StoredObjectKey key, SeekType seekType)
[9/18/2022 2:04:38 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.CollectionEnumerator.Find(Int64 id)
[9/18/2022 2:04:38 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.PopulateCollectionTable()
[9/18/2022 2:04:38 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.PerformCollection()
[9/18/2022 2:04:38 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.Collect(String fileName, Boolean disableThrottle, Boolean createDbBackups, TraceOp traceLevel)
[9/18/2022 2:04:38 AM] [ INFO]    at Updater.Run()
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMain(HINSTANCE__* hInst, HINSTANCE__* hInstPrev, UInt16* pwzCmdLine, Int32 nCmdShow)
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMainCRTStartup()
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMainStub()
[9/18/2022 2:04:38 AM] [ INFO] Unhandled Exception: System.InvalidOperationException: Error getting IDBCreateCommand - HR = 0x0
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteErr.LogAndThrowException(Int32 hr, String msg, Object[] args)
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteCommand.CreateCommand(IUnknown** ppunk)
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteCommand.InitNativeCommand()
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteSession.ExecuteSql(String sql)
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.SqlLite.SqlLiteSession.DeleteCollectionInfoTable()
[9/18/2022 2:04:38 AM] [ INFO]    at MediaCenter.Store.OleDB.ObjectStore.DeleteCollectionInfoTable()
[9/18/2022 2:04:38 AM] [ INFO]    at Microsoft.MediaCenter.Store.StoreObjectCollector.Collect(String fileName, Boolean disableThrottle, Boolean createDbBackups, TraceOp traceLevel)
[9/18/2022 2:04:38 AM] [ INFO]    at Updater.Run()
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMain(HINSTANCE__* hInst, HINSTANCE__* hInstPrev, UInt16* pwzCmdLine, Int32 nCmdShow)
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMainCRTStartup()
[9/18/2022 2:04:38 AM] [ INFO]    at wWinMainStub()
[9/18/2022 2:04:38 AM] [ERROR] Error using mcupdate.exe to perform database garbage cleanup. Exit code: -532459699
[9/18/2022 2:04:38 AM] Exiting PerformGarbageCleanup(). FAILURE.
[9/18/2022 2:04:39 AM] Entering ImportMxfFile() for file "c:\epg123\output\epg123.mxf".
[9/18/2022 2:10:54 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[9/18/2022 2:10:54 AM] Exiting ImportMxfFile(). SUCCESS.
[9/18/2022 2:10:54 AM] Entering VerifyLoad()
This second section that shows a sample of the output in the trace log file (there are quite a few instances of the exception that is shown) may suggest that my channel lineup has changed since I last went through to hide channels I don't care about (I hide any of the premium channels we don't subscribe to and low def versions of channels we get in HD, but haven't gone through to update the list in quite a while):

Code: Select all

[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching STZESPS to channel 363 (363) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Skipped matching WWDPSD to channel 46 (46) due to channel already having an assigned listing.
[9/18/2022 2:18:16 AM] [ INFO] Matching FIOS4K4 to channel 1494 (1494)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:16 AM] [ INFO] Matching FIOS4K6 to channel 1496 (1496)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:16 AM] [ INFO] Matching FIOS4K8 to channel 1498 (1498)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:16 AM] [ INFO] Matching FIOS4K9 to channel 1499 (1499)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:16 AM] [ INFO] Matching WFXT to channel 8 (8)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:16 AM] [ INFO] Matching WWDPSD to channel 46 (46)
[9/18/2022 2:18:16 AM] [ INFO] Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel.
   at Microsoft.MediaCenter.Guide.MergedChannel.AddChannelListings(Channel csiChannel)
   at epg123Client.WmcStore.SubscribeLineupChannel(Int64 lineupChannelId, Int64 mergedChannelId)
[9/18/2022 2:18:17 AM] [ INFO] Matching VZ26 to channel 116 (116)

Space

Posts: 2587
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#4

Post by Space » Sun Sep 18, 2022 5:16 pm

It's interesting that you were able to import the MXF file this time, but those errors during the garbage cleanup and likely the errors during the channel matching are due to database corruption, but Gary would know the best course of action.

Also, I mentioned that a Rebuild of the database may restore backups from 5 days ago, but backups are done prior to the garbage cleanup, so I suppose they may be current backups, although I have no idea if those backups would be corrupted as well since they were made from an already corrupted database... Given that, I don't recall ever reading here in these forums of anyone having an issue with the database backups being corrupted (or at least it causing any real problems).

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Sun Sep 18, 2022 6:19 pm

Yah, this definitely looks like a corrupt database. Best action would be [Rebuild WMC Database] ... BUT, before you do that, try to create a backup using the [Backup] button and see if it succeeds.

I'm definitely confused as to why it tries to match STZESPS on channel 363 so many times.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Sun Sep 18, 2022 9:42 pm

If you do manage to get a backup, could you send the zip file to support@garyan2.net? I'd like to see what is going on there with the matching. Thanks.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#7

Post by gsr » Sun Sep 18, 2022 11:18 pm

garyan2 wrote:
Sun Sep 18, 2022 9:42 pm
If you do manage to get a backup, could you send the zip file to support@garyan2.net? I'd like to see what is going on there with the matching. Thanks.
The backup worked. You should have a copy in your inbox.

User avatar
garyan2

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

HTPC Specs: Show details

#8

Post by garyan2 » Sun Sep 18, 2022 11:50 pm

Well, I kinda see why it was trying to match the STZESP channel so many times. Did you really run TV Setup for each tuner individually? Rather than have all 9 CableCARD tuners added at the same time you did 9 separate scans for each tuner?
Last edited by garyan2 on Mon Sep 19, 2022 12:02 am, edited 1 time in total.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#9

Post by gsr » Sun Sep 18, 2022 11:58 pm

garyan2 wrote:
Sun Sep 18, 2022 11:50 pm
Well, I kinda see why it was trying to match the STZESP channel so many times. Did you really run TV for each tuner individually? Rather than have all 9 CableCARD tuners added at the same time you did 9 separate scans for each tuner?
They were added at the same time. I configured this system several years ago, but do recall having some trouble getting all the tuners to merge (or whatever the term is).

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Mon Sep 19, 2022 12:05 am

If they were scanned together in TV Setup, then the merge would have happened automatically. Weird.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#11

Post by gsr » Mon Sep 19, 2022 12:52 am

garyan2 wrote:
Mon Sep 19, 2022 12:05 am
If they were scanned together in TV Setup, then the merge would have happened automatically. Weird.
Yeah, I would have expected that as well, but I remember having problems with it at the time. It’s long enough back that I don’t remember all the details.

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#12

Post by gsr » Mon Sep 19, 2022 8:34 pm

After the database backup was successful, I restored the database from the backup and initiated a guide update. There were no fatal errors (I still see the "Exception thrown during SubscribeLineupChannel(). You cannot map a UserHidden channel." exceptions). The nightly guide update also ran without any fatal errors this morning.

I also remembered what the deal is with the tuners being setup separately. At the time, the CableCard tuners were being shared with another PC running WMC. If we let all 9 tuners configure automatically on both computers, they were in the same order and we would get "tuner not found" popup modal windows on one computer or the other every time CableCard recordings started at the same time on both PC's as they would both try to use the same tuner. To avoid those, I ended up configuring the tuners in reverse order on my computer, which meant I had to add them 1 at a time. What's weird is that OTA recordings don't have the same problem when trying to get a tuner.

User avatar
garyan2

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

HTPC Specs: Show details

#13

Post by garyan2 » Tue Sep 20, 2022 3:58 am

Near as I can tell, the exceptions are due to the merging. I'm not sure what makes those channels unique among all the others... will have to take a closer look.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

gsr

Posts: 96
Joined: Thu Sep 06, 2012 12:50 am
Location:

HTPC Specs: Show details

#14

Post by gsr » Tue Sep 20, 2022 11:04 am

garyan2 wrote:
Tue Sep 20, 2022 3:58 am
Near as I can tell, the exceptions are due to the merging. I'm not sure what makes those channels unique among all the others... will have to take a closer look.
As long as everything is working, I can live with those. It's quite possible they have been in the log all along and I hadn't noticed them until now.

Post Reply