This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
When running through the configure option for K2 Blackpearl Setup manager it will complete successfully. However, some DLLs within the following directory will be updated back to their original Install version.
K2 Blackpearl 4.7:
C:\Program Files (x86)\K2 blackpearl\Bin\ControlPack Controls
C:\Program Files\K2\Bin\ControlPack Controls
Version before the configuration has been run:
Version after configuration has been run on the same server:
-You are currently running the Setup.exe from the current install directory for K2. For example: "C:\Program Files (x86)\K2 blackpearl\Setup\Setup.exe" or from the start menu > K2 > Blackpearl Setup Manager.
-You have confirmed that the Modify or Repair options were not done in the meantime.
If you are running the installer from the original K2 Blackpearl 4.7 RTM Install media this is expected to cause some DLL changes because the original install has no idea what specific CU or FP has been installed on your environment and will reference the original DLLs in it's directory. The path for that could be similar to "C:\Users\Administrator\Downloads\K2 Installation Package (4.16060.2000.3)\1. K2 blackpearl (4.16060.2000.3)\Installation\Setup.exe"
K2 recommends that after running the Configure option on the K2 Setup Manager, that you also re-run the update wizards for your current CU/FP that is installed on the server. This will get the DLLs within the ControlPack Directory back up to the correct version for your current CU/FP. This is expected behavior as during the configure process we re-register multiple controls via these DLLs.
Refer to the following documentation where it is mentioned you should rerun the relevant FP and CU for your environment: