Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.3, 4.3.1, 4.3.2, 4.3.3
-
None
Description
When the collation settings of the Confluence database is set to a case sensitive according to the documentation: https://confluence.atlassian.com/display/DOC/Database+Setup+for+SQL+Server, but the master database is in a different collation, the following error appears in the log:
java.sql.SQLException: Invalid object name 'SYS.OBJECTS'.
The problem appears in version 4.3.x, where ActiveObjects were introduced.
Either Confluence has to handle the different collation settings for the master database or the documentation has to be updated to mention the collation settings requirement for the master database too.
Workaround
The solution is to change the collation of the master database to the same collation as the Confluence database. Please note that this may affect other applications that use the same database server, so it shall be applied with caution!