Video Screencast Help
New Company Name and Logo Announced. Learn More.

LiveUpdate error

Created: 15 Dec 2009 • Updated: 17 Jun 2010 | 3 comments

I am getting " LiveUpdate returned a non-critical error. Available content updates may have failed to install." error every day (every 2 hours)
is there a way to see what exactly failed to install? This is on a WIndows 2003 Standard SP2 with SEP 11.0.5


Comments 3 CommentsJump to latest comment

Vikram Kumar-SAV to SEP's picture

this can be due Decomposer Engine failure
or virus definition corruption. 

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search use it.

Rafeeq's picture

Event ID 13: LiveUpdate returned a non- critical error. Available content updates may have failed to install

This event shows up in the Symantec Endpoint Protection client's Windows Event Log. It indicates that a 20010007 (see DbgView section above) has occurred. This error condition should be resolved as soon as new sequence number for that content becomes available. To figure out which content package is failing, look at the DbgView output and Log.LiveUpdate. If the Symantec Endpoint Protection client in question receives new content via Symantec Endpoint Protection Manager, TPM or GUP and you are sure that a new, corrected content packages is available, but are still seeing the error, some things you might try:

    • Verify that the new content package has been downloaded to Symantec Endpoint Protection Manager by checking that it is listed under the LiveUpdate Content policy
    • Verify that you have the content type in question set to "use latest available" in the LiveUpdate Content policy
    • Verify that intermediate steps in the content flow are up and running (the GUP, an internal LiveUpdate server, Third Party Management software)
    • If the content type that is failing is not AV Definitions or IPS Signatures, try deleting the cached revisions of that content under c:\Program Files\Symantec\Symantec Endpoint Protection\ContentCache. This will force a full package to come down via your enabled content channel(s) rather than a delta package.
  • follow this document to get the issue resolved

AravindKM's picture

Try by repairing the SEP client from add/remove programs... 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind