EPG123 Failed to import .mxf file

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
Curly73

Posts: 2
Joined: Thu Jul 09, 2020 4:42 pm
Location:

HTPC Specs: Show details

EPG123 Failed to import .mxf file

#1

Post by Curly73 » Thu Jul 09, 2020 7:24 pm

After working flawlessly for about four months, I suddenly have empty guide data. Upon checking trace.log I find errors started around June 25th. It appears that EPG123 is updating properly but the client is unable to import the .mxf file into WMC. Here's the latest from trace.log:

Code: Select all

[7/9/2020 1:43:49 AM] [ INFO] Completed EPG123 update execution. SUCCESS.
[7/9/2020 1:43:49 AM] [ INFO] epg123 update execution time was 00:00:49.3428867.
[7/9/2020 1:43:50 AM] ===============================================================================
[7/9/2020 1:43:50 AM]  Beginning epg123 client execution. version 1.3.8.20
[7/9/2020 1:43:50 AM] ===============================================================================
[7/9/2020 1:43:50 AM] [ INFO] Beginning epg123 client execution. 2020-07-09 05:43:50Z
[7/9/2020 1:43:50 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: False
[7/9/2020 1:43:50 AM] Entering importMxfFile() for file "c:\programdata\garyan2\epg123\output\epg123.mxf"
[7/9/2020 1:44:23 AM] [ INFO] Error: The following error was encountered while processing the file. Aborting.
[7/9/2020 1:44:23 AM] [ INFO] UId UIdI_UIdKey: InsertRow() failed (attempt 0 of 10) for (1,
......1F00) - HR = 0x80004005, minor = 25104, 2049, 0, 0, "", "", ""
[7/9/2020 1:44:23 AM] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[7/9/2020 1:44:23 AM] Exiting importMxfFile(). FAILURE.
[7/9/2020 1:44:23 AM] [ERROR] Failed to import .mxf file. Exiting.
Any advice/suggestions would be GREATLY appreciated. Thanks!

User avatar
Scallica

Posts: 2745
Joined: Mon Jun 06, 2011 7:09 pm
Location: USA!

HTPC Specs: Show details

#2

Post by Scallica » Thu Jul 09, 2020 7:45 pm

Start by posting in the correct subforum :lol:
HTPC Enthusiast / Forum Moderator - TGB.tv Code of Conduct

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Thu Jul 09, 2020 7:56 pm

The client is failing to import the guide listings due to a corruption in your database. With the disappearance of the MS servers to provide the maintenance package, this is the side effect of not being able to keep the database healthy. This side effect was the impetus to v1.3.8.x so that EPG123 could do the maintenance.

Your options based on the trace.log information is to run the below in a command prompt and wait for it to complete. If it completes without error, then you should be able to import the mxf file without a problem.

Code: Select all

START /WAIT C:\Windows\ehome\mcupdate.exe -dbgc -updateTrigger
If it fails, or you still can't import guide listings, then the only other option is to open the client and click the [Rebuild WMC Database] button.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
IT Troll

Posts: 801
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#4

Post by IT Troll » Fri Jul 10, 2020 9:40 am

garyan2 wrote:
Thu Jul 09, 2020 7:56 pm
The client is failing to import the guide listings due to a corruption in your database. With the disappearance of the MS servers to provide the maintenance package, this is the side effect of not being able to keep the database healthy.
Whilst that may the case here, lack of maintenance doesn't necessarily result in corruption. I ran my database without any maintenance or issues for 2.5 years.

In fact I think we are seeing an increase in database issues now that maintenance is active. Perhaps this is uncovering latent issues, or perhaps something else is going on.
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1.1

User avatar
garyan2

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

HTPC Specs: Show details

#5

Post by garyan2 » Fri Jul 10, 2020 3:31 pm

Though I don't disagree, I would be hesitant to say we don't need to do maintenance. There was a considerable uptick in reported failures to import due to a corrupted database from users setup WMC after the MS servers were shutdown. I think the size of the database is a good indicator of how long you can go without it. Large database may only be able to go 3-4 months without maintenance while the smaller ones may be able to go for years.

I do agree, presently, that running maintenance on these large databases that haven't had maintenance run in a while is exposing the corruptions/errors. Only time will tell if my current method sufficiently addresses the problem.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

User avatar
IT Troll

Posts: 801
Joined: Sun Nov 27, 2011 9:42 am
Location: Edinburgh, UK

HTPC Specs: Show details

#6

Post by IT Troll » Fri Jul 10, 2020 5:59 pm

Database maintenance is usually a good thing. I just know I have had more problems with it enabled than disabled.
I am willing to give it another shot though. I am hoping that disabling updates is the answer.
The only loss is recording history which is difficult to explain to the other half once repeats start getting scheduled.
Are you a Recorded TV HD user or want to give it a try? Check out the new community-made update; Recorded TV HD v2.1.1

User avatar
garyan2

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

HTPC Specs: Show details

#7

Post by garyan2 » Fri Jul 10, 2020 7:24 pm

If you are up to an experiment, you can change a registry setting to use the "old" database again which will have your old recording history. The registry is [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\Epg] "EPG.instance". Change the value to the database number Y from C:\ProgramData\Microsoft\ehome\mcepgX-Y.db from when the recovery happened. If you do this, then you should probably reboot the machine just to make sure everything is linked to the old database.

I believe it will work, but next time the maintenance runs it may have the same issue and initiate another recovery. I haven't done much/any experimentation on this so don't know if there any other effects. You can always revert back to your current database with the registry above if it doesn't work out (and reboot).
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

Curly73

Posts: 2
Joined: Thu Jul 09, 2020 4:42 pm
Location:

HTPC Specs: Show details

#8

Post by Curly73 » Fri Jul 10, 2020 11:12 pm

Gary,
Thanks for your prompt response! I ran the command line script you suggested and the only response I received was the message "Windows Media Center Store Manager is Restarting". I didn't get any error messages so I assume it ran successfully? At any rate, still no joy with importing the guide listings. I then performed a Database Rebuild and a manual import and all seems to be fine now assuming there are no problems with automatic update. I really appreciate your help with this. Thanks again!

Markinsac

Posts: 19
Joined: Sat Sep 20, 2014 8:36 am
Location:

HTPC Specs: Show details

#9

Post by Markinsac » Sat Jul 11, 2020 6:19 am

I'm seeing a message that the imported MXF file is 25.73 hours old.

Also error message "[ERROR] Unhandled exception caught from epg123.exe. message: Object reference not set to an instance of an object."

User avatar
garyan2

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

HTPC Specs: Show details

#10

Post by garyan2 » Sat Jul 11, 2020 6:45 pm

Markinsac wrote:
Sat Jul 11, 2020 6:19 am
I'm seeing a message that the imported MXF file is 25.73 hours old.

Also error message "[ERROR] Unhandled exception caught from epg123.exe. message: Object reference not set to an instance of an object."
Please follow this thread (viewtopic.php?f=99&t=13130) for updates on this.
- Gary
Keeping WMC alive beyond January 2020. http://epg123.garyan2.net

Post Reply