Schema Evolution failed

Any messages that schema evolution (a kind of database update) failed, or the schema version is not the expected version, mean, that beaTunes' internal database is stuck in the format of an older version than the one you are currently running. In this state beaTunes will not function properly.

This can have one of two causes:

1. Before schema evolution the database was already in bad shape. That's why the evolution failed.
   
2. Something in the evolution itself went wrong.

A solutions that always works, is to recreate the database. To do so, you have to delete the database and rebuild it from scratch. Starting with beaTunes 4.0.2, you can do this by simply clicking on Recreate Database in the Tools menu. Data that was only stored in the database will be lost.

Update from beaTunes 3 to beaTunes 4 (or from beaTunes 4 to beaTunes 5)

Before upgrading the database to the beaTunes 4 (or 5) format, beaTunes makes a backup copy of the database. This backup is located in:

• Windows C:\Users\<username>\AppData\Local\tagtraum industries\beaTunes\database Backup Unknown Version
• macOS /Users/<USERNAME>/Library/Application Support/beaTunes/Database Backup Unknown Version

If you would like to try the schema evolution again, please

• Stop beaTunes
• Go to the directory C:\Users\<username>\AppData\Local\tagtraum industries\beaTunes\ or /Users/<username>/Library/Application Support/beaTunes/
• Delete the directory Database or database
• Duplicate/copy the directory Database Backup Unknown Version and change the duplicates' name to Database (OS X) or database (Windows)
• Start beaTunes 4 (or 5)

The schema evolution should then restart.

If this still does not lead to success, you have to delete the database and rebuild it from scratch. Starting with beaTunes 4.0.2, you can do this by simply clicking on Recreate Database in the Tools menu. Data that was only stored in the database will be lost.