When upgrading an AX 2012 database which is non-default collation to the new version, failures occur in DB synchronize


If upgrading an AX 2012 database to the new version, and the AX 2012 database uses a non-default collation (the default is SQL_Latin1_General_CP1_CI_AS) then you may experience errors during database synchronize process when running the database upgrade process.

Specifically this was found to be the case for the Danish_Norwegian_CI_AS collation as it treats aA as a separate character. This was causing a failure when syncing some views which used mixed casing for some fields (like DataAreaId) when they should have been using upper casing.


The fix is to correct metadata for the affected views to not use the incorrect mixed-case aA for DataAreaId and other similar fields.

More information

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.