- March 10, 2006
- 4,434
- 1,897
- Moderator
- #11
I deleted C:\ProgramData\Team MediaPortal\MediaPortal\Database\TVSeriesDatabase4.db3, uninstalled the TVSeries Plugin, restarted my computer, reinstalled the plugin, tried to enter the configuration of the plugin when I got the screen which I posted a few posts back. So I think that this is a fresh new database??? I wanted to just start from scratch and get TVSeries working again as the wife is waiting to watch a new show.
I try to use the default screen settings. I did upgrade from 1.3RC to the official 1.3 and I also let it use the titan skin since this seems to be stable since it is with the official 1.3
Should I go back to the previous skin?
Check the "TVSeries.SkinSettings.xml" file indeed as @ltfearme pointed out. It contains the logo rules and other rules, which might have become corrupted for some reason. If you attach a zip version of that file it might assist in figuring out what happened to it and how to prevent it in the future .
The reason this problem kept coming back to you, is because when you uninstall a plugin it leaves the skin files alone. During re-installation the XML skinfile in question has a newer filedate then the plugin wants to install, which causes it to skip over it (it assumes you made modifications to it that you wish to keep).
Switching to a 'different' skin would solve that, but if you go into your active skin folder just delete all the XML files that look like "TVSeries.xxxxxx.xml" along with "TVSeries.xml" itself. Then delete "C:\ProgramData\Team MediaPortal\MediaPortal\Database\TVSeriesDatabase4.db3" again and reinstall the TVSeries plugin ontop. This will then put all the new skin files into the right place which should not re-corrupt the database.
PS: There is no reason to reboot when doing this, because MediaPortal does not have an OS lock on the files you are replacing.
PPS: You might have NTFS journal corruption, so I strongly advice to run a scan. Via "Computer" -> right click "C:" drive and then "Tools" tab -> "Check Now" button -> "Automatically fix for file system errors" enabled, you can run the same test. If OS has a lock on the drive, you will get a message and just use the "Schedule disk check" option and then reboot, so during pre-boot it can run the scan properly and fix any errors.