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.
The K2 Workflow reports show instances in running status even though they have completed. This is due to deadlocks that occur in the K2 Server when updating high volumes of item references.
A SQL error may occur: “deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction”
The user may see process instances in “running” state on the K2 workspace site, even when they have completed.
- Ensure you have K2 Five (5.0) installed.
- Download and Install the K2 Five (5.0) September 2018 Cumulative Update from K2 Partner and Customer Portal.
- Download the K2 Five (5.0) September 2018 Cumulative Update FP12 from K2 Partner and Customer Portal.
- Install the K2 Five (5.0) September 2018 Cumulative Update FP12 to apply the fix.
- It is recommended to refresh the browser cache.