Cannot install Nov CU after .Net 4.7.1 is installed
kbt142606
PRODUCTIssue
After a windows update has installed .Net 4.7.1, we are experiencing issues:
https://help.k2.com/support-services/kb002127
Following the above KB, we have logged a support ticket and received the cold fixes.
When we run the cold fixes, some errrors appears.
The errors will include, but are not limited to:
"Logged Error: Target did not complete successfully: Register_Control_AutoComplete
Logged Error: Target did not complete successfully: Register_Control_HTMLEditor
Logged Error: Target did not complete successfully: Register_Control_ListBox
Logged Error: Target did not complete successfully: Register_Control_MultiChoice
Logged Error: Target did not complete successfully: Register_Control_Reporting
Logged Error: Target did not complete successfully: Register_Control_Tree
Logged Error: Target did not complete successfully: Register_Control_Worklist
Logged Error: Target did not complete successfully: Register_Control_ManagementControlPack
Logged Error: Could not start service
Logged Error: Target did not complete successfully: K2 Package and Deployment for SharePoint.kspx
Logged Error: Target did not complete successfully: K2 blackpearl Service"
Symptoms
The service is not starting due to the Windows update that was installed.
The fix for this is in FP8. But, FP8 is dependent on the Nov CU... which we can't fully apply due to the service not running.
So the service will appear to be 'stuck'.
Resolution
To resolve this issue please follow these steps:
1. Backup K2 DB and K2 install dir
2. Run the Nov CU, knowing that it will error (save the installer log)
3. Run FP8 (save the installer log)
4. Next, test to see if the service starts.
5. If it does, run the Nov CU again (save the installer log)
6. If it passes, run FP8 (save the installer log)
After step 4, run the CU and FP again, because there is no guarantee that the CU and FP have been properly applied.
If the service does not start at step 4, or errors are shown in steps 5 or 6, please log a support ticket (if one is not already open) and attach any installer logs up to that time (for this run) and the K2 host server log.
