Skip to main content
Nintex Community Menu Bar

Failed upgrade from 4.6.11 to 4.7. Conversion failed when converting from a character string to unique identifier.

  • February 16, 2021
  • 0 replies
  • 19 views
  • Translate

MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • Nintex Employee
  • 667 replies
 

Failure to upgrade from 4.6.11 to 4.7. Conversion failed when converting from a character string to unique identifier

kbt137620

PRODUCT
K2 blackpearl 4.6.11 to 4.7
TAGS
Installation
Upgrading
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
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

In certain scenarios, the K2 Blackpearl upgrade to 4.7 from 4.6.11 will not complete with the following script failure appearing.

Logged error:

"Script execute failed: System.Exception: Script execution exception: Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Conversion failed when converting from a character string to uniqueidentifier.
Component.ExecuteTarget: 08:32:16:>> Logged Error: Target did not complete successfully: SourceCode.Data.Form.4.16060.7.5.PostUpgrade.sql"

Symptoms

This is a known issue when upgrading to 4.7 from 4.6.11.

Resolution

Please log a support ticket to obtain the fix.
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