CPUSE process could not patch some files on the machine. This could be caused by several factors:
- A previously installed hotfix may have changed some files without properly generating a backup.
- A previously installed hotfix may have changed some files, but the original files were not found in the backup.
- Some files may have been manually changed on the machine.
(1) Action plan:
-
Determine which files CPUSE failed to patch from the Patching Error Report. This report contains information about all files that were not patched and the reason for each file.
-
Take the necessary steps based on the failure reason.
To get the Patching Error Report:
-
If the installation that failed was a hotfix package - refer to the bottom of the hotfix's installation log (in the /opt/CPInstLog/ directory) to see the Patching Error Report.
-
If the installation that failed was a minor version update - refer to the bundle's installation log file (in the /opt/CPInstLog/ directory) to get the path of the installation log of the failed package. Patching Error Report will be found at the bottom of that log.
(2) Procedure:
-
If the files that CPUSE failed to patch were part of an installed Hotfix - uninstall the Hotfix and retry your installation.
-
If the files that CPUSE failed to patch were modified by a user - try to get the original files (if they were saved).
-
Contact Check Point Support to get the relevant CPUSE Full package.
-
If none of the above reasons are applicable - contact Check Point Support and provide the following:
- Patching Error Report from Gaia Portal
- Complete contents of /opt/CPInstLog/ directory
(3) Related solutions: