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.
An error appears at the last part of database consolidation: Constraint, Proc, Index.
"Database consolidation was cancelled or failed. See log for more information."
The installer log generated by the tool shows the error "Could not re-encrypt."
It points to a particular entry in the [CustomUM].[User] table inside the K2SQLUM database where UserID=0 fails to get decrypted.
Prior to running the consolidation tool, remove the entry on the table which fails to get decrypted:
DELETE FROM [K2SQLUM].[CustomUM].[User] WHERE [UserID] = 0
If this does not help, please ensure that the connection string (VariableValue
) points to the SQL server instance where the single K2 database will be hosted:
SELECT [VariableToken], [VariableValue] FROM [K2HostServer].[HostServer].[Configuration]
WHERE VariableToken LIKE '%CONNECTIONSTRING%'
Should there be a need to update a connection string, kindly log a K2 Support Ticket as direct manipulation of data stored inside the K2 database without the supervision of a K2 personnel could put you in an unsupported state.