Environment | Ucommerce 9.0.0 - 9.6.0 |
Question/Problem description | After upgrading to 9.6.0 the scratch indexer won't run with the error "Cannot resolve collation conflict between Latin1_General_CI_AS and another langauge". |
Steps to reproduce | Install or upgrade to 9.6.0 and have your SQL server set in another collation than Latin1_General_CI_AS |
Error message | "Cannot resolve collation conflict between Latin1_General_CI_AS and another langauge". |
Resolution | The problem has really existed since the first Ucommerce version was released, but now is the first time the issue appear. The reason is a hardcoded collation on the table uCommerce_DataTypeEnum. To fix the issue run the sql script below against your Ucommerce database. ALTER TABLE uCommerce_DataTypeEnum ALTER COLUMN [Value] NVARCHAR(1024) COLLATE DATABASE_DEFAULT |
Workaround | There's no workaround at this point. You need to apply the steps outlined in the resolution section of this article |
Cannot resolve the collation conflict between Latin1_General_CI_AS and Latin1_General_CI_AS Print
Modified on: Wed, 22 Jun, 2022 at 3:24 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.