Reconfigure the Environment

Once you have your K2 environment up and running, you may need to modify components or change configuration settings. You accomplish this by re-running the Setup Manager to add or remove components, or to change configuration settings.

When reconfiguring your installation, be sure to use the Setup Manager that is installed with your K2 system, found by default (in clean installations) at "%ProgramFiles%\K2\Setup\Setup.exe".

If any change is made to the K2 Designer web site, you must clear your browser cache for the changes to reflect.
After installing a Cumulative Update (CU) or Fix Pack (FP), any time you use the Reconfigure, Update, or Modify option in the Setup Manager to make changes to your installation, you must reinstall the same or latest CU and FP.
If you have installed the K2 Five (5.5) November 2021 CU, and you use the Update option, the current installation's system files revert to the original versions and the Setup Manager may cause an error. For more information see the section Version Conflict warning.

Use the information in the following topics to reconfigure your K2 environment.

Features Description
Configure Re-configures the existing K2 installation, running through the screens as in the Simple Installation.
Modify Modifies the existing installation by either adding or removing components.
Remove Removes the existing K2 components from your environment.
Update Use Update to update your installed version of K2 to the same version as the Setup Manager. This reverts all system files back to the original version of the Setup Manager but keeps your configuration files and any custom changes you have made to them.
Removing a K2 server from a farm does not remove references to that node in the K2 database. The farm will continue to poll the removed node in the server cluster. Contact support to remove all references to the node in the K2 database.

Version Conflict warning

When attempting to run the K2 Setup Manager with the Update option on a K2 Five (5.4) or (5.5) environment with a CU/FP applied, it may fail on the K2 Database component. To avoid this, you must use the Configure option to make changes to the environment. The Configure option keeps all system file version numbers as they are, while the Update option reverts system files back to the original version.

If you use the Update option and encounter the problem, this is the error seen in the installer trace logs:

MigrateDatabase.Execute: Logged Error: Failed: System.IO.FileLoadException: Could not load file or assembly 'System.ValueTuple, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'System.ValueTuple, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' ---> System.IO.FileLoadException: Could not load file or assembly 'System.ValueTuple, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'System.ValueTuple, Version=4.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'

When you try to run the Setup Manager again, it raises a Version Conflict warning, and clicking Launch returns the same warning, so it is not possible to move forward:

If this happens, contact support for a solution.