Code Fix: K2 Server ceases to function correctly when LIM API is used to change process version number

  • 16 February 2021
  • 0 replies
  • 12 views

Userlevel 3
Badge +8
 

Code Fix: K2 Server ceases to function correctly when LIM API is used to change process version number

KB000481

PRODUCT
K2 blackpearl
SEE ALSO

K2 blackpearl Downloads Page

TAGS
K2 API
K2 Server
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.

 

Introduction

The K2 Server fails when the LIM API is used to change the version number of a process instance.

 

 

Error Scenario

The K2 Server when either in a standalone or clustered environment will be unable to function correctly and fail where more than one version of the same process has been deployed in the same environment, and the LIM API is used to change the version number of one of the process instances.

The error can be reproduced by following the steps below:
  1. Deploy a process twice to create two different versions of the same process
  2. Start and stop instances of the two processes
  3. Use the API to change the version number of the process instance

 

 

Error Messages

The following error message applies to this article:

  • 15101 Error occurred, ERROR: 24143 Unable to Forward Cluster Message, server entry 0 not found

 

 

Error Resolution

This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.

The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx

 


0 replies

Be the first to reply!

Reply