Error in trace log

An evolving, supported alternative to Rovi
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html
Post Reply
User avatar
RobsterUK

Posts: 49
Joined: Mon Apr 29, 2013 10:10 am
Location: Cornwall, UK

HTPC Specs: Show details

Error in trace log

#1

Post by RobsterUK » Sat Aug 26, 2017 9:18 am

Hi,

Hoping to resolve this issue from the trace log.
Currently have quite a lot of my guide missing simply stating 'To Be announced'

Here's the relevant output from the trace.log

Code: Select all

[26/08/2017 10:06:40] [ERROR] Error: The following error was encountered while processing the file. Aborting.
[26/08/2017 10:06:40] [ERROR] RowSet::DeleteRow(Program_keywords Program_keywordsI_ParentChildKey) - DeleteRows() failed for handle 1 - HR = 0x80040e21, minor = 28574, 3640, 0, 0, "", "", ""
[26/08/2017 10:06:40] [ERROR] Error using loadmxf.exe to import new guide information. Exit code: -1
[26/08/2017 10:06:40] [ERROR] Failed to import .mxf file. Exiting.
Looks as though its failing to import the xmf, but is this error from the EPG123 xmf file or the Media Center side?

Would be grateful if someone could help out here,

Thanks in advance!

User avatar
RobsterUK

Posts: 49
Joined: Mon Apr 29, 2013 10:10 am
Location: Cornwall, UK

HTPC Specs: Show details

#2

Post by RobsterUK » Sat Aug 26, 2017 9:40 am

I backed up the epg123.xmf file & deleted it. Then manually ran the updater again. Still got the same error.

User avatar
garyan2

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

HTPC Specs: Show details

#3

Post by garyan2 » Sat Aug 26, 2017 2:27 pm

This typically means your database is corrupted. The loadmxf.exe tool is provided by Microsoft to import the mxf file into the database and the error is being generated during that operation. Is the error immediate? or after some time from entering the import operation?

Before doing anything drastic, I would recommend running the garbage collector on the database by running "C:\Windows\eHome\mcupdate.exe -dbgc" from an elevated prompt. This can take some time, so wait for the process to end before trying epg123 again.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
RobsterUK

Posts: 49
Joined: Mon Apr 29, 2013 10:10 am
Location: Cornwall, UK

HTPC Specs: Show details

#4

Post by RobsterUK » Sat Aug 26, 2017 2:39 pm

Thanks garyan2, the import gets to about 60% before failing.

I'll try the garbage collector and post back. Will be a couple of hours until I can do this.

Sent from my Nexus 5X using Tapatalk

User avatar
RobsterUK

Posts: 49
Joined: Mon Apr 29, 2013 10:10 am
Location: Cornwall, UK

HTPC Specs: Show details

#5

Post by RobsterUK » Sat Aug 26, 2017 5:34 pm

OK I'm now having issues trying to run the garbage collector.

From the Event log the client maintenance starts, takes 5 minutes then fails when trying to import the EPG listings.
I get thie error:
"Failed to retrieve EpgListings (Error: HeadendId 42 is invalid.)"

When the updater crashes it pops up an error message dialogue box with these details in.

Code: Select all

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	mcupdate.exe
  Problem Signature 02:	6.1.7601.17514
  Problem Signature 03:	4ce7af4a
  Problem Signature 04:	mcstoredb
  Problem Signature 05:	6.1.0.0
  Problem Signature 06:	4ce7c734
  Problem Signature 07:	b8
  Problem Signature 08:	9c
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2057
If this is relevant, I'm running Windows 7 with EPG123 ver 1.0.2

User avatar
garyan2

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

HTPC Specs: Show details

#6

Post by garyan2 » Sat Aug 26, 2017 6:13 pm

RobsterUK wrote:OK I'm now having issues trying to run the garbage collector.

From the Event log the client maintenance starts, takes 5 minutes then fails when trying to import the EPG listings.
I get thie error:
"Failed to retrieve EpgListings (Error: HeadendId 42 is invalid.)"

When the updater crashes it pops up an error message dialogue box with these details in.

Code: Select all

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	mcupdate.exe
  Problem Signature 02:	6.1.7601.17514
  Problem Signature 03:	4ce7af4a
  Problem Signature 04:	mcstoredb
  Problem Signature 05:	6.1.0.0
  Problem Signature 06:	4ce7c734
  Problem Signature 07:	b8
  Problem Signature 08:	9c
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2057
If this is relevant, I'm running Windows 7 with EPG123 ver 1.0.2
Well, this is all interesting. I'm not sure why the garbage collector is trying to retrieve EpgListings, may be due to another error (you used the -dbgc in the command, correct?). HeadendId 42 is what I use for EPG123 ... it is an invalid MS/Rovi id so I'm not surprised by that message.

An mcupdate crash is pretty bad. I would say your database is very corrupted. I would try the following in order until you can successfully import listings:

1. Run "C:\Windows\ehome\mcupdate.exe -ObjectStoreRecoveryTask". Wait for it to complete. Try to import epg123.mxf.

2. *You will lose recording history when doing this*
Download the latest epg123 portable zip file here. Extract epg123Client.exe and run it. Click the [Database Rebuild] button and when prompted, navigate to your epg123.mxf file to import it.

3. Nuke it. Install the latest EPG123 (you know v1.0.2 is nearly a year old now) and perform a Step 1: Clean Start per the installation guide.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io

User avatar
RobsterUK

Posts: 49
Joined: Mon Apr 29, 2013 10:10 am
Location: Cornwall, UK

HTPC Specs: Show details

#7

Post by RobsterUK » Sat Aug 26, 2017 7:17 pm

garyan2 wrote:
RobsterUK wrote:OK I'm now having issues trying to run the garbage collector.

From the Event log the client maintenance starts, takes 5 minutes then fails when trying to import the EPG listings.
I get thie error:
"Failed to retrieve EpgListings (Error: HeadendId 42 is invalid.)"

When the updater crashes it pops up an error message dialogue box with these details in.

Code: Select all

Problem signature:
  Problem Event Name:	CLR20r3
  Problem Signature 01:	mcupdate.exe
  Problem Signature 02:	6.1.7601.17514
  Problem Signature 03:	4ce7af4a
  Problem Signature 04:	mcstoredb
  Problem Signature 05:	6.1.0.0
  Problem Signature 06:	4ce7c734
  Problem Signature 07:	b8
  Problem Signature 08:	9c
  Problem Signature 09:	PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2057
If this is relevant, I'm running Windows 7 with EPG123 ver 1.0.2
Well, this is all interesting. I'm not sure why the garbage collector is trying to retrieve EpgListings, may be due to another error (you used the -dbgc in the command, correct?). HeadendId 42 is what I use for EPG123 ... it is an invalid MS/Rovi id so I'm not surprised by that message.

An mcupdate crash is pretty bad. I would say your database is very corrupted. I would try the following in order until you can successfully import listings:

1. Run "C:\Windows\ehome\mcupdate.exe -ObjectStoreRecoveryTask". Wait for it to complete. Try to import epg123.mxf.

2. *You will lose recording history when doing this*
Download the latest epg123 portable zip file here. Extract epg123Client.exe and run it. Click the [Database Rebuild] button and when prompted, navigate to your epg123.mxf file to import it.

3. Nuke it. Install the latest EPG123 (you know v1.0.2 is nearly a year old now) and perform a Step 1: Clean Start per the installation guide.
Yes I was running the task with the -dbgc switch.
I'm pleased to say that I only had to complete the first step and it has imported the guide successfully.

I must admit that I haven't checked for any updates for EPG123 since I switched over to using it almost 18 months ago. I did read about the caveat depending on the .net version installed on the PC for 1.1.5 update. I will check this out and run the update when I have sufficient time to ensure it runs smoothly.

Thank you so much for taking the time to help me figure this out & thanks for the great bit of software Image

Sent from my Nexus 5X using Tapatalk

Post Reply