< class="prominent-subhead ">

Code Fix: An error occurs when you start a K2 Workflow instance on a Cluster environment

~~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 you assign a User Task to a new group which has not been resolved by the K2 Server, and you start an instance of the K2 Workflow on a Cluster environment, an error occurs.

Error Message


The following error occurs: “A server could not obtain a database lock to resolve the identity for '{0}' in the configured timeframe”.

Resolution

The fix is available in the following K2 versions:

K2 4.7 December 2019 Cumulative Update K2 Five (5.0) December 2019 Cumulative Update K2 Five (5.1) November 2018 Cumulative Update K2 Five (5.2) May 2019 Cumulative Update K2 Five (5.3)
Fix Pack 1 X X X X
  1. Ensure you have the correct K2 version and/or Cumulative Update installed. See KB001893 to see what Fix Pack level you have installed.
  2. Download the latest Fix Pack using the links in the table above for the version you require.
  3. Install the Fix Pack to apply the fix.