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:

1. Stop the DSM service.
2. Go to the SQL server hosting the DSM database.
3. Go to the DSM database.
4. Click Properties > Options > Collation.
5. Change the collation used to "SQL_Latin1_General_CP1_CI_AS".
6. 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:

1. Back up the DSM database.
2. Manually update the DSM database schema.
3. Apply Deep Security Manager 9.5 SP1 Patch 1 Build 9.5.6008 or higher.