2012-07-17, 22:29
I had a problem recently with this plugin, but was able to solve it. I post it here in case anyone has a similar problem, so they at least can see one avenue of approach.
The problem I had was that all of the TV menus returned an error when clicked. Movies and its submenus worked fine, but one couldn't get to any TV shows or episodes. Eventually, I suspected that it was a db problem, and sure enough, the tv0.db had a size of 0 kb. It's located (Windows 7) in:
\Users\%USERNAME%\AppData\Roaming\XBMC\userdata\addon_data\plugin.video.amazon\
where %USERNAME% is the login used for windows where XBMC settings are stored. All you have to do is
1. Close XBMC
2. Delete tv0.db (or rename in case you're worried you might break something)
3. Start XBMC
4. Open Amazon plugin. The db will be reloaded, presumably via download.
I assume this will also work if you can't see movies, or both tv and movies. Just delete the db(s) with XBMC closed. Or, to be extra careful, copy the db's with another name and then delete. I also assume this solution will work if the db(s) are corrupted rather than 0 size, but have not run across that scenario.
The problem I had was that all of the TV menus returned an error when clicked. Movies and its submenus worked fine, but one couldn't get to any TV shows or episodes. Eventually, I suspected that it was a db problem, and sure enough, the tv0.db had a size of 0 kb. It's located (Windows 7) in:
\Users\%USERNAME%\AppData\Roaming\XBMC\userdata\addon_data\plugin.video.amazon\
where %USERNAME% is the login used for windows where XBMC settings are stored. All you have to do is
1. Close XBMC
2. Delete tv0.db (or rename in case you're worried you might break something)
3. Start XBMC
4. Open Amazon plugin. The db will be reloaded, presumably via download.
I assume this will also work if you can't see movies, or both tv and movies. Just delete the db(s) with XBMC closed. Or, to be extra careful, copy the db's with another name and then delete. I also assume this solution will work if the db(s) are corrupted rather than 0 size, but have not run across that scenario.