Bug? TV no longer working - Unknown error occured (1 Viewer)

[msj33]

MediaPortal Version: 1.1.1
MediaPortal Skin: StremedMP
Windows Version: Windows 7
CPU Type: AMD X3 +5200, 2.7 Ghz
HDD: WD 1TB
Memory: 2 Gb Kingston
Motherboard: Asrock AliveNF6G-GLAN
Video Card: ASUS AEH4350 SILENT
Video Card Driver: ATI Catalyst 10.9
Sound Card: ATI HD Audio throughHDMI
Sound Card AC3: HDMI
Sound Card Driver: latest
1. TV Card: Terratec Cinergy HD DVB-C PCI
1. TV Card Type: DVB-C
1. TV Card Driver: 1.1.1.901
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: SAF 5.0 (Cyberlink)
MPEG2 Audio Codec: SAF 5.0 (Cyberlink)
h.264 Video Codec: SAF 5.0 (Cyberlink)
Satelite/CableTV Provider:
HTPC Case: Silverstonetek LC11M
Cooling: NorthQ
Power Supply: 300 watt
Remote: IMON Harmony
TV: Panasonic 42" PX70
TV - HTPC Connection: HDMI

I have been running mepo every day past year without any issues.

Now all of a sudden, i cannot start TV any longer - displays: unknown error occured

seems like epg keeps looping and tv.log seems to have errors

Is this a possible bug or do yo have any ideas what to do

I have attached log files

 

[msj33]

Error seems to be the same as : https://forum.team-mediaportal.com/...-error-occured-when-attempting-view-tv-86513/

Anyway to fix this - And what could be the cause of this?

Seems like something is crashing Mepo Database!

/Morten

 

[frenskeman]

heej msj33,

you can try to do the following to repair the mysql database,, it's an older post of ashoft which i use when i recieve this error :

Since running MP Version 1.1. beta I have had a number of corruptions to program.myi.
So I have been have used the following to repair mysql database files
(happened a couple of times using previous version. You have to type it in cmd prompt.

CD C:\Program Files\MySQL\MySQL Server 5.1\bin
mysqlcheck mptvdb --auto-repair -e -u root -p

when asked password = "MediaPortal"

I also had it in 1.1.1, however since the update to 1.1.2 it didn't happen anymore. hope it also works for you