While applying service packs or cumulative patches, the installation failed or rolled back. You then checked the tmpatch.log and rename the file that the patch failed to replace. However, the patch setup still failed to replace another file.
When a service pack or patch is applied, it stops the related services, replaces specific files, and then starts the services. Issues in patch installations usually happen when another process or application is using the file so that it is locked with the process and could not be replaced by the patch setup.
To see what processes or applications are using the file:
- Download the process explorer tool from Microsoft.
- Stop all the related Trend Micro services on the server.
- Stop the World Wide Web Publishing service.
- If you are applying a patch for Control Manager (TMCM) or OfficeScan, go to task manager and then kill or stop dbserver.exe.
If not, proceed to step 5.
- Run the process explorer tool and then click the Agree button.
- On the menu, click Find.
- Select handle or dll, and then enter the installation folder name of the product you are patching.
For example, if it is TMCM, type the TMCM installation directory.This search will display any file inside the product directory that are still locked or being used. You can temporarily kill or stop the processes or services.
- Run the patch application again.
If the issue still persists, it may be affected by the database issue. Collect and submit the following to Trend Micro Technical Support.
- TMPatch.log located on C drive.
- TMCM database for further checking.