search cancel

Definitions stop updating with "latest full not found" after upgrading to Endpoint Protection Manager 12.1.5 (RU5)


Article ID: 161358


Updated On:


Endpoint Protection


After upgrading Symantec Endpoint Protection Manager (SEPM) to 12.1.5 (RU5), one or more of the content types fail to update on the managers. Clients no longer receive updates for the affected content types from the SEPM.  There are various errors in the SesmLu.log indicating an issue publishing the definitions into the database. When a JDB is manually dropped, it is processed by SEPM, but fails to update into the database and the file extension changes from .jdb to .jdb.err. Checking the inetpub\content folder, it fails to publish the new definition.

ConfigServer-0/1.log contains errors similar to:

[date/time] THREAD 93 SEVERE: Error: File not found: Latest full not found: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Inetpub\content\{42B17E5E-4E9D-4157-88CB-966FB4985928}\141212001\Full
at com.sygate.scm.server.consolemanager.requesthandler.ConfigServerHandler.saveLUContent(


This was introduced by the content optimization changes made in SEPM 12.1.5. The problem happens when one SEPM updates content through LiveUpdate or Intelligent Updater (IU) while another SEPM in the same site begins publishing content. When this happens, a content remediation function is called, which incorrectly removes the latest revision of the content from the database.


This issue is fixed in Symantec Endpoint Protection Manager 12.1.6.  For information on how to obtain the latest build of Symantec Endpoint Protection, read
TECH 103088: Download the latest version of Symantec Endpoint Protection