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.
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.
Upgrading from K2 Five to 5.1 fails with a number of errors being highlighted within the configuration analysis. These errors are also highlighted within the K2 set up trace log.
You can access the trace log via the following directory: Program Files (x86) > K2 Blackpearl > Set up > Logs
The following errors are displayed:
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: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'Authorization.Object' and the index name 'UX_Authorization_Object_ClassID_Hash_IsClassObject'.
The duplicate key value is (64b0b584-8c45-4cce-839e-8daaa2ae16d8, 0x3c602a1c2455f7219a1abd46d8e66f980e6cad7949d93f0ed30de2f7a9854261, 0).
This issue has been resolved by applying the latest 5.1 installer
which can be found on Portal.k2.com.