Cannot login Endpoint Protection Manager console after upgrade

Products

• Endpoint Protection

Issue/Introduction

Cannot login Symantec Endpoint Protection Manager (SEPM) console after upgrade SEPM.

Error message:

The version of Symantec Endpoint Protection Manager that you are trying to run is not the same as the version you are trying to connect to.
This situation can occur between replication partners, or between the remote console and the management server.
Upgrade any replication partners, or download the correct version of the remote console from the management server.

C:\Users\<logon user>\AppData\Local\Temp\SEPM_INST.log:

MSI (s) (50:D4) [08:43:14:057]: Re-applying security from existing file.
Info 1603.The file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\scm-ui.jar is being held in use.  Close that application and retry.
...
MSI (s) (50:D4) [08:43:14:130]: Verifying accessibility of file: scm-ui.jar
Info 1903.Scheduling reboot operation: Deleting file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\scm-ui.jar. Must reboot to complete operation.
Info 1902.Scheduling reboot operation: Renaming file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\TBMAE6C.tmp to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\scm-ui.jar. Must reboot to complete operation.

 

You can find several .tmp files in <SEPM install folder>\tomcat\webapps\ROOT\clientpkg folder.

Cause

Another windows user was logged on SEPM console during upgrade.

Resolution

Reboot OS to replace SEPM console files.

In some cases, a Repair will need to be run in order to correct the issue.