First, thanks for the great service to us WMC holdouts!
I have two machines running full epg123. I occasionally get database corruption. I have pretty much learned how to fix it using the 4 steps you provided:
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.
I just got another one after installing 1.3.6.0. I was wondering if you could give some insight as to what causes the corruption. Is there something on the machine that could be causing it, or just inherent to the beast.
Thanks!
Tim
Database Corruption Causes
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
- Posts: 12
- Joined: Wed Jul 05, 2017 6:55 am
- Location: Arizona
- HTPC Specs:
- garyan2
- Posts: 7438
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
- HTPC Specs:
For those that may stumble in here, I'll give some reference to the OP's post.
When we talk about database corruption, this will present itself to EPG123 as a failure to import the MXF file using loadmxf.exe which is a WMC executable.
The steps outlined are progressive, so if you experience a suspected corrupt database, then you perform steps 1 and 2. If the MXF file still fails to import, then try step 3. If step 3 fails, then step 4 is nearly guaranteed to work... otherwise you have more problems than just the WMC guide.
The other way a database corruption can present itself is when you open WMC and you get a prompt about "Windows Media Center has corrected a problem...." It is still unclear to me why this occurs, but the "crash" is only when you open WMC and it fails some check of the database. At that point it will create a new database and you will have to import guide listings again. There has been some discussion of this here, here, and I'm sure many other places.
When we talk about database corruption, this will present itself to EPG123 as a failure to import the MXF file using loadmxf.exe which is a WMC executable.
The steps outlined are progressive, so if you experience a suspected corrupt database, then you perform steps 1 and 2. If the MXF file still fails to import, then try step 3. If step 3 fails, then step 4 is nearly guaranteed to work... otherwise you have more problems than just the WMC guide.
The other way a database corruption can present itself is when you open WMC and you get a prompt about "Windows Media Center has corrected a problem...." It is still unclear to me why this occurs, but the "crash" is only when you open WMC and it fails some check of the database. At that point it will create a new database and you will have to import guide listings again. There has been some discussion of this here, here, and I'm sure many other places.
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io