Use of cookies by SourceCode Technology Holdings, Inc. We use cookies to deliver our online services. Details and instructions on how to disable those cookies are set out here. By continuing to use this website you agree to our use of our cookies unless you have disabled them.

Install the K2 Five (5.0) September 2018 Cumulative Update FP11 to apply the fix.

Considerations

After installing the Fix Pack, any new workflows will work when you migrate an instance to another version.

Two Possible solutions for workflows in broken state:

If Live Instance Management has been attempted only once.

Navigate to your K2 Database where you will change the [ExecutingProcID] value located in the [Server].[ProcInst] table, edit the top 200 rows of the table and change the value to the previous ID before Live Instance Management was attempted. The previous value of the [ExecutingProcID] will in most cases be the value of [ProcID] for that process.

Following the same procedure as above the [ExecutingProcID] will also need to be change to the same previous version in the [ServerLog].[ProcInst] table.

Restart all your host servers.

Please note: that this will only work if you have not deleted any previous versions of your process.

If Live Instance Management has been attempted more than once follow these steps:

If your process instance 19 was migrated from version 1 to version 3 and then to version 4.

Run the following script to get the previous values for both [ExecutingProcID] and [ProcID].

Please note: If you do not use the default K2 as your database name, you will need to change the [K2] database name to the name of your database in the script below before it can be run, for example [Your Database Name].[Server].[Proc]