Symantec Endpoint Protection Manager is trying to download content from Symantec LiveUpdate servers rather than internal LiveUpdate Administrator 2.x server


Article ID: 156112


Updated On:


Endpoint Protection


LiveUpdate Administrator (LUA) is used as a central point for content downloading in the company. Symantec Endpoint Protection Manager (SEPM) is configured to download definition updates from LUA.

When LiveUpdate is manually executed on SEPM, contents get updated. Schedule LiveUpdate on SEPM is however failing with error code 4, because it tries to reach Symantec LiveUpdate servers and there is no Internet connectivity on SEPM.

Settings.liveupdate shows Symantec LiveUpdate servers as HOSTS. Reinstall LiveUpdate did not help.

Release Notes show there is a known defect fixed in RU7 MP1, but both SEPM and clients are already using this build of SEP.


"Error: LiveUpdate encountered one or more errors. Return code = 4" in LiveUpdate status in Symantec Endpoint Protection Manager





Generating a client settings host file for Windows LiveUpdate clients on the LUA 2.x server and placing it into the SEPM's LiveUpdate folder is one method for ensuring that both the SEPM and its SEP 11 client will retrieve materials from the LUA server.

  1. Login to the LUA console
  2. Go to Configure > Client settings
  3. Add a new line, which will contains all Distribution Centers SEPM should use
  4. Click on "Export Windows Settings" and "Export Java Settings" button
  5. Copy exported liveupdt.hst file into LiveUpdate install folder ("C:\Program Files (x86)\Symantec\LiveUpdate" or "C:\Program Files\Symantec\LiveUpdate")
  6. Copy exported Settings.Hosts.LiveUpdate into LiveUpdate data folder ("C:\ProgramData\Symantec\LiveUpdate" or "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate")
  7. Wait for Scheduled LiveUpdate to be ran on SEPM


Applies To

  • SEPM do not have access to Internet-based Symantec LiveUpdate servers.
  • SEPM RU7 MP1 with local SEP RU7 MP1 client, configured to update from the internal LUA 2.x server