Troubleshooting Cannot resolve the collation conflict

SQL_Latin1_General_CP1_CI_AS is required

Issues regarding a server, database or table using any collation other than the SQL_Latin1_General_CP1_CI_AS collation does NOT fall under SMA, it falls under Professional Services. MC requires that you use SQL_Latin1_General_CP1_CI_AS for everything.

If you get an error Cannot resolve the collation conflict between "<anything>" and "SQL_Latin1_General_CP1_CI_AS" you have a situation where your MS SQL server and the database or table are not able to do a comparison. When running with Accruent MC it is mandatory that the SERVER, all databases and all tables use the US centric SQL_Latin1_General_CP1_CI_AS collation. While it isn't a problem for MCe, that is irrelevant if you are running Accruent MC.

If you are running a MS SQL Server that is setup with a different collation, and you require it because a different program requires a different collation - then you need to set up a second MS SQL server, so you have one that 'has' to have <whatever> collation and your Accruent MC one that 'has' to have the SQL_Latin1_General_CP1_CI_AS collation. If you have no other applications that require <your current> collation - then you obviously could install just one and use the SQL_Latin1_General_CP1_CI_AS collation.

But to be clear, if you have 2 problems, one that requires the server be set to <whatever> collation and Accruent MC that requires the SQL_Latin1_General_CP1_CI_AS collation.

Note that if you use the Asset Pro Solutions/ITIQPro installer/upgrader, we so far have been able to fix the install/upgrade packages, most recently MC 2025, to install even if you don't use SQL_Latin1_General_CP1_CI_AS. But we haven't been able to fix all the cases when running, and they vary from version to version.

You may be able to use MCe (it handles any collation) to get around areas that MC needs the SQL_Latin1_General_CP1_CI_AS. But you are better off following Accruent's rules to avoid problems.

The collation sequence:

on the SERVER
on the reg database
on the ent database(s)

Must be set to the US standard collation SQL_Latin1_General_CP1_CI_AS.

SQL_Latin1_General_CP1_CI_AS

This SQL_Latin1_General_CP1_CI_AS collation is defined ass:

SQL_: this is a SQL Server collation, not a, for example, Windows collation
Latin1: Uses the Latin 1 character set (ASCII) with Code Page 1252.
CP1: Windows ANSI Code Page 1252; Code Page 1252 (also known as CP-1252 or windows-1252) is an 8-bit character encoding designed by Microsoft for Windows, primarily used for Western European languages. It is a superset of ISO 8859-1 (Latin-1), differing by replacing the undefined control characters in the 80–9F hex range with printable characters such as curly quotation marks, dashes, the euro sign (€), and the French florin (ƒ).
CI (Case Insensitive): Treats uppercase and lowercase letters as equal (e.g., 'A' equals 'a').
AS (Accent Sensitive): Treats accented characters as distinct from their non-accented counterparts (e.g., 'A' differs from 'Ä').

Must NOT be set to any other collation, not in the server, not in the databases. Cannot even be set to the "rest of the world" English collations "~~Latin1_General_CI_AS~~" or "~~Latin1_General_100_CI_AS~~".

How to check, run this SQL:

SELECT SERVERPROPERTY('collation') AS ServerCollation;

Isn't it installed by default with SQL Server?

Here's the problem, based on tests, most recently in 2025 and 2026 with MS SQL and MC 2025, it looks like if Microsoft decides your server is in the USA it installs SQL_Latin1_General_CP1_CI_AS on the server and subsequently on the databases and, in the case of Accruent, most significantly for issues, on temporary databases.