Skip to main content
Nintex Community Menu Bar

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

  • February 16, 2021
  • 0 replies
  • 61 views

Anelle
Nintex Employee
Forum|alt.badge.img+11
  • Nintex Employee
  • 13 replies
 

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

KB002196

PRODUCT
K2 blackpearl 4.7
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, 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 4.7 installed.
  2. Download and Install the K2 4.7 November 2017 Cumulative Update from K2 Partner and Customer Portal.
  3. Get the K2 4.7 November 2017 Cumulative Update FP10 from Regional Support.
  4. Install the K2 4.7 November 2017 Cumulative Update FP10 to apply the fix.

 

Translate
Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings