by oneoffbeat » Sun Apr 14, 2019 4:51 am
Installed the new version and immediately started getting SQL database error, something about drop table not working and database being locked. Symptoms were that the library update was stuck and the error message kept returning over and over whether I chose to cancel, retry or ignore it, also first time I launched the new version it requested program elevation, which I haven't seen MM doing for quite a while. Then tried to re-install 4.1.23.1881 just over the newer version, but the database was still broken (obviously) so I recovered both the User\AppData\Roaming\MediaMonkey and Program (x86)\MediaMonkey folder contents from backup files and then installed 4.1.23.1881 again and things went back to normal. I also launched Windows 10 compatibility troubleshooter, but without any help. Sorry, didn't save the screen shot or more detailed wording from the error message, since I went through the install and recovery process twice already in panic mode, so I hope my loose description about the error is giving away enough clues to make some conclusions.
Installed the new version and immediately started getting SQL database error, something about drop table not working and database being locked. Symptoms were that the library update was stuck and the error message kept returning over and over whether I chose to cancel, retry or ignore it, also first time I launched the new version it requested program elevation, which I haven't seen MM doing for quite a while. Then tried to re-install 4.1.23.1881 just over the newer version, but the database was still broken (obviously) so I recovered both the User\AppData\Roaming\MediaMonkey and Program (x86)\MediaMonkey folder contents from backup files and then installed 4.1.23.1881 again and things went back to normal. I also launched Windows 10 compatibility troubleshooter, but without any help. Sorry, didn't save the screen shot or more detailed wording from the error message, since I went through the install and recovery process twice already in panic mode, so I hope my loose description about the error is giving away enough clues to make some conclusions.