Instance Configuration process to set up the Central/Local repository results in error: "Cannot resolve collation conflict for concatenation operation." This error may display when updating statistics to the LiteSpeedLocal or LiteSpeedCentral database.
The collation of the msdb database must match the collation for the master database. LiteSpeed utilizes both the master DB and the msdb for it's setup and processing, so the collations must be the same.
WORKAROUND:
Delete the LiteSpeedLocal and LiteSpeedCentral databases. Rerun Instance Configuration, reregister the servers/instances in the LiteSpeed Console.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center