When you upgrade the Deep Security Manager (DSM) to the latest version, you encounter the following error message:
Unable to access Database schema. Installation cannot continue
The Server0.log shows the following information:
Oct 03, 2014 3:57:23 PM com.thirdbrigade.manager.core.Core processInitDatabase
SEVERE: ThID:10|TID:0|TNAME:Primary|UID:-1|UNAME:|Unable to start.
The software version (9.5.2456) did not match the schema version (9.0.5500).
If this is one manager node of many, please ensure that you run the installer package to upgrade.
The service will not be able to start until the software is upgraded.
Oct 03, 2014 3:57:23 PM com.thirdbrigade.manager.core.Core processInitDatabase
SEVERE: ThID:10|TID:0|TNAME:Primary|UID:-1|UNAME:|Unable to start database:
java.lang.Exception: Unable to start. The software version does not match the schema version
The issue is due to the collation setting of the database. The DSM database supports the SQL_Latin1_General_CP1_CI_AS setting. Applying this setting makes the server treat strings as case-insensitive, accent-sensitive, kanatye-insenstive, and width-insensitive. The SQL sort order for Unicode Data is 52 on the Code Page and 1252 for the non-Unicode Data.
To resolve the issue, use the supported SQL_Latin1_General_CP1_CI_AS server collation:
- Stop the DSM service.
- Go to the SQL server hosting the DSM database.
- Go to the DSM database.
- Click Properties > Options > Collation.
- Change the collation used to "SQL_Latin1_General_CP1_CI_AS".
- Start the DSM service.
For more information, you may refer to this Microsoft KB article: Set or Change the Server Collation.
When the installer fails to modify the DSM database schema, check the database integrity and manually upgrade the database schema:
- Back up the DSM database.
- Manually update the DSM database schema.
- Apply Deep Security Manager 9.5 SP1 Patch 1 Build 9.5.6008 or higher.
