![]() tmp files in \tomcat\webapps\ROOT\clientpkg folder. 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. Info 1903.Scheduling reboot operation: Deleting file C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\clientpkg\scm-ui.jar. MSI (s) (50:D4) : Verifying accessibility of file: scm-ui.jar 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. MSI (s) (50:D4) : Re-applying security from existing file. Upgrade any replication partners, or download the correct version of the remote console from the management server.Ĭ:\Users\\AppData\Local\Temp\SEPM_INST.log: ![]() This situation can occur between replication partners, or between the remote console and the management server. 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. Symantec Endpoint Protection Manager console Logging on to the console locally To log on to the console locally Go to Start > Programs > Symantec Endpoint Protection Manager > Symantec Endpoint Protection Manager. ![]() Cannot login Symantec Endpoint Protection Manager (SEPM) console after upgrade SEPM.
0 Comments
Leave a Reply. |