#1 Global Leader in Data Resilience

Veeam Service Provider Console fails to connect to restored VSPC database due to collation conflict

KB ID: 4255
Product: Veeam Service Provider Console | 6.0 | 7.0 | 8.0 | 8.1
Published: 2022-02-04
Last Modified: 2024-12-02
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When attempting to connect Veeam Service Provider Console to an existing VSPC database the following error occurs:
Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict between "<instance_collation>" and "<database_collation>" in add operator.
Where the value of <instance_collation> is equal to the collation of the target SQL Instance, and <database_collation> is equal to the collation of the target database.
Screenshot of collation error
Example of Error
(The exact collations mentioned in the error may vary.)

Cause

Starting in Veeam Service Provider Console v6, it is not possible to connect to a database if that database and the instance hosting it have different collation settings.

Solution

It is not possible to safely perform collation conversion of the VSPC database.

A new SQL Instance must be created with a collation that matches the VSPC database. After that SQL Instance is created, the VSPC database you were attempting to connect to must be moved/restored to that new collation-matching instance. When the database and instance collation match, you may connect Veeam Service Provider Console to the database.

More Information

Checking Database and Instance Collation

For more information see View Collation Information in the SQL Documentation.

Information about the database and instance collation can be found within their properties. Within SQL Server Management Studio right-click on either the instance or database and select Properties. Database collation information is listed under the heading Maintenance, and instance collation is found in the row labeled Server Collation.

 

screenshot of database collation
Database Collation example
screenshot of sql instance collation
Server (Instance) Collation example
Alternatively, if SQL Server Management Studio is unavailable use the following SQL Query via sqlcmd to list the SQL Instance's collation and the collation of all databases on that instance.
SELECT CONVERT (varchar(256), SERVERPROPERTY('collation'));
SELECT name, collation_name FROM sys.databases;
example of sqlcmd
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.