< class="prominent-subhead ">

Code Fix: A SQL error occurs when the K2 database and SQL server collation differs

~~repeating-content.html~~
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue Description

When executing a joined SmartObject when the K2 database Collation differs from the SQL Server Collation, a SQL error returns.

Error Message

The error states: “Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation”.

Resolution

  1. Ensure you have K2 Five RTM installed.
  2. Get the K2 Five RTM FP7 from Regional Support.
  3. Install the K2 Five RTM FP7 to apply the fix.