"Database Version 0" Error when logging into Synbiosis software
Posted by Stephen Barnard, Last modified by Stephen Barnard on 26 February 2021 03:37 PM
NOTE : Throughout this article, I will refer to ProtoCOL 3 software, but the same steps are valid for Protos 3 or ChromaZona. If a step specifies "ProtoCOL 3" in a folder or group name, then simply substitute "Protos 3" or "ChromaZona".
There are several possible reasons for this error :
1 : Windows User Permission.
The SQL Database is locked down, so only designated users can access it.
This includes basic functions, such as querying the Database version.
If the Windows User does not have permission to access the Database, then the ProtoCOL 3 software will be unable to query the Database version and will return "Database Version 0".
Ensure that the logged in Windows User is in one of the User Groups, as per this guide :
2 : Database does not exist.
Similar to the above, the software will query the Database Server and if there is no Database of the name specified, the server will return "Database Version 0".
Run the application DatabaseUpdater.exe. This application can be found in the same folder as the ProtoCOL 3 installation. The location is typically one of these:
Note: there are two files that have "DatabaseUpdater" in their name. You'll know you've double-clicked the right file if the following window appears:
Press the "..." button, to the right of the "Backup Path" string.
You should then see this :
Press the "Create New Database" button, next to the "Database Name" field (a "drive" icon, with a red and yellow "burst" icon in the upper left corner). The software will attempt to create a new Database, named according to the text in the "Database Name" field.
The software should report to you whether it has been successful or not.
If the Database was created, press ok on the report box, ok in the Data Paths box and then "update" in the Database Updater box. The software should sequentially update the database to the required version and then report its completion.
Close the Database Updater dialog and start the ProtoCOL 3 software. Hopefully it should now proceed to the login screen.
If the Database failed to be created, then either the Database name already exists and there is a configuration issue with the ProtoCOL 3 software and the SQL Database, the Windows User does not have permission to create the Database, or the SQL Server is not running or not installed.
At this point, I would suggest contacting email@example.com for further assistance.
Database Version 0 Errors can also be caused by the PC name being changed, or the Database no longer being on the PC it was created on. See article "Computer name mismatch when moving database from one PC to another"