Guide fails to import

[dlpalumbo]

Hi,

Everything running fine for months, years even, then scheduled update began returning failures. I updated to newest version and installed. This worked once and everything fine, but when I when tried to close client it hung, so I had to force close it. After that WMC had no guide. Tried to reinstall and get this error.

Code: Select all

[10/13/2018 5:43:10 PM] Entering importMxfFile() for file "C:\ProgramData\GaRyan2\epg123\output\epg123.mxf"
[10/13/2018 5:43:44 PM] [ INFO] Error: The following error was encountered while processing the file. Aborting.
[10/13/2018 5:43:44 PM] [ INFO] ScheduleEntry: InsertRow() failed (attempt 0 of 10) for (1, 3680C80100001500010000000100000003A00100000005000000000000000000575F040000000E0000000000000000008AC2070000001D00005055A3F230D60800B81905FB30D6080000000000000000000000000000000000FFFF000000000000000000000000000000000000000000000000000000000000000000000000000000000000FFFF00000000000000000000000000000000) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""
[10/13/2018 5:43:45 PM] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[10/13/2018 5:43:45 PM] Exiting importMxfFile(). FAILURE.
[10/13/2018 5:43:45 PM] [ERROR] Failed to import .mxf file. Exiting.

When set to 21 days, the error occurs at 38%. 7 days 76%. I day 96%. Tried clearing cache, rebuilding database. Not sure how to recover.

Thanks for help,

Dan

[dlpalumbo]

So I uninstalled, deleted all epg directories, reinstalled and did a clean start. It worked.

Not sure how it got balled up, but doing above saved the day.

One quick question. I have 2 8.1 machines which do recordings. They both stopped updating at same time. Not sure why. When I did the clean start on 1 machine, when I got to step 2, WMC insisted on downloading database even though I "did not agree". I let it sit for a long time, then closed wmc and went to step 3. I used EPGClient restore to get WMC config back and eventually got update to run. Other machine didn't try to download database.

Any explanation for this?

Thanks for help,

Dan

[garyan2]

A loadmxf.exe error during import usually points to a database corruption. Having 2 machines fail at the same time is certainly interesting, but I have no idea how EPG123 or the MXF file could have caused it. Do both machines run EPG123 in full mode, or does only 1 machine create the MXF file and both import the same MXF file? When the client hung when you were trying to close it, what were you doing prior (Tweak WMC, Add channel, ...)? Based on your description, it looks like it was the hanging of the client and your forced closure which corrupted the database. Were there any errors before the loadmxf error that could point to the original problem?

WMC will always do the "download" step during setup regardless of the ToS agreement. It is not downloading any guide information, but is downloading updated information concerning the transmit modulation and frequencies available based on geographic location. Sometimes it is very slow during this step for really no benefit since WMC already has a baseline to work with... it's just looking for updates. If it fails to do this step, you can actually go back to the ToS screen, unplug your network cable, again deny the ToS, and when it gets to the "download" step again it will timeout in a few seconds(?) and allow you to proceed (just remember to plug the network back in). Just a quirk and something to keep in mind when MS pulls the plug on WMC.

For future reference when encountering a situation like this, I would recommend the following actions to try and restore functionality (stop when problem goes away):

1) From a command prompt, run "start /wait c:\windows\ehome\mcupdate.exe -uf -dbgc".
2) Using EPG123, clear the cache and do a [Save & Execute].
3) Using EPG123 Client, click the [Rebuild WMC Database].
4) Using EPG123 Client, click the [Client Setup] button for a clean start.

#1 will possibly fix any WMC database corruption if that is the problem.
#2 will clear out any corrupted cached files used to create the mxf file if that is the problem.
#3 will delete the current WMC database and restore your tuner setups, scheduled recordings, and custom configurations.
#4 will nuke the WMC database and ehome folder and start over. You will still be able to restore your scheduled recordings and custom configurations.

You could actually do #1 and #2 at the same time.

[dlpalumbo]

Do both machines run EPG123 in full mode, or does only 1 machine create the MXF file and both import the same MXF file?

Both machines run full mode. But they were at same EPG version level, updated at same time.

Were there any errors before the loadmxf error that could point to the original problem?

The first errors on both machines were failed schedule updates with a -1 status return. I didn't really look into this and just thought an update to current EPG version would fix things. When the EPG updates failed I began looking at the error logs. My last resort was a clean start and I was really spooked when WMC stubbornly tried to download guide. After clean start, the EPG Save and Execute ran to completion and the schedule updated successfully.

WMC will always do the "download" step during setup regardless of the ToS agreement.

That's strange because second machine didn't do download and gave me a screen I can't recall but said something to the effect that I could always get guide later. Good trick to unplug cable...

#2-#4 were basically the steps I used. Didn't know about the mcupdate ploy.

Thanks for EPG and your help. It has run very well and reliably. I am always amazed at how well it works. Nothing more satisfying to me than a good piece of programing.

[garyan2]

You don't have both of their schedules set for the same time do you? There can only be 1 active token at a time for Schedules Direct so they will have to be spaced apart in time to allow one to finish before the other starts.

[dlpalumbo]

You don't have both of their schedules set for the same time do you?

Oops. I Certainly do. Thanks and a tip of the hat.

Dan.