---
title: "LeaseControl - Cannot resolve collation conflict"
canonical: "https://servicedesk.maxgeo.com/space/MAXGEO/1065123863/LeaseControl%20-%20Cannot%20resolve%20collation%20conflict"
format: markdown
---
**Problem:**
When conducting various operations, an error is returned regarding "Cannot resolve the collation between..." and goes on with further detail including a description of the relevant collations.
**Cause:**
This is not an LeaseControl error. Rather, the SQL Server hosting the database is of a different collation to the SQL (LeaseControl) Database. (For non-techies: the collation can be considered the method used to categorise and locate data). This ordinarily occurs when a database is restored to a different SQL Server than where it was originally created - though the error may not be immediately apparent.
**Resolution:**
(a) Move the database to an SQL Server of the same collation. (To determine collation, open up SQL Management Studio. Right-click on either the SQL server name, and separately the database name, and go to "Properties".)
(b) There are various scripts that can be run to effectively change the collation of the database to match the server - try using Google to find the right one ensuring you use only trusted sites. You will need to know what the database and SQL server collations are (and which one is which). Please refer instructions in resolution (a) above.
*Request for further assistance are ordinarily directed to your company's IT team, noting that we can provide further support should this be required. As this is not a LeaseControl support matter, fees may apply. Please direct queries to s**[servicedesk@maxgeo.com](mailto:support@maxgeo.com)**. We can improve our service to you if you advise this article has been reviewed and which resolution is preferable.*