A database script enhancement run on existing pre K2 4.5 databases when upgraded to K2 4.5 throws an error if orphaned entries are found.
The pre K2 4.5 installation’s database is updated with an alter script which changes specific tables within the database to disallow null values. However, if there were pre - existing orphaned entries within the database already, their presence would cause an error and the alter script would be prevented from running.
|Note: An orphaned entry is a database record that has no valid or verifiable process instance information to associate with it. These orphaned entries must be removed from the database before the alter script can be run.|
|Important: The error message(s) displayed below are known to occur and error messages similar to these may be expected; but may not be limited to the cited examples.|
Cannot insert the value NULL into column 'ActionId', table 'K2Server.dbo._ActionActInstRights'; column does not allow nulls. UPDATE fails.
The statement has been terminated.
To correct this error, any existing orphaned entries must be removed. As a precaution, a check is made to ascertain for sure that there are is process information associated with the orphaned entries and then they are deleted.
The latest K2 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx.