Endpoint Protection

Here is the information form the log.

October 2012 12:55:24 BST:  Symantec Endpoint Protection Win64 11.0.6005.562 (English) is up-to-date.    [Site: Iris]  [Server: HMUK00S042]
10 October 2012 12:55:21 BST:  Symantec Endpoint Protection Win64 11.0.4014.26 (English) failed to update.  [Site: Iris]  [Server: HMUK00S042]
10 October 2012 12:55:10 BST:  Symantec Endpoint Protection Win32 11.0.6005.562 (English) is up-to-date.    [Site: Iris]  [Server: HMUK00S042]
10 October 2012 12:55:06 BST:  Symantec Endpoint Protection Win32 11.0.4014.26 (English) failed to update.  [Site: Iris]  [Server: HMUK00S042]
10 October 2012 12:55:00 BST:  TruScan proactive threat scan engine Win32 11.0 is up-to-date.    [Site: Iris]  [Server: HMUK00S042]
10 October 2012 12:54:57 BST:  TruScan proactive threat scan commercial application list Win32 11.0 failed to update.  [Site: Iris]  [Server: HMUK00S042

They are not uptodate...  Last update was the 2nd October..

Symantec Endpoint Protection Manager 11.x is not updating 32 or 64 bit virus definitions

http://www.symantec.com/business/support/index?page=content&id=TECH104721

I'd highly recommend reviewing the below article for how to troubleshoot LiveUpdate on a SEPM

http://www.symantec.com/docs/TECH105924

The article contains instructions on how to locate the log files (log.liveupdate and sesmlu.log) that would assist us in tracking down your issues (if the article doesn't fix it for you...)

Hello,

What version of SEPM 11.x are you running?

On what OS is SEPM 11.x installed?

Is the SEPM 11.x taking updates from Liveupdate Administrator OR Symantec Liveupdate (Internet)?

Are you using any Proxy on the machine?

I would suggest you to check these Articles:

Symantec Endpoint Protection: LiveUpdate Troubleshooting Flowchart

Symantec Endpoint Protection Manager 11.x is not updating 32 or 64 bit virus definitions.

How to update definitions for Symantec Endpoint Protection Manager (SEPM) using a .jdb file

If these articles does not help, please upload us the log.liveupdate from the SEPM server.

Hope that helps!!

Hi,

Try to reboot the server and then manually run liveupdate by logging into SEPM -->servers-->local site-->download liveupdate.

also upload logs.liveupdate .

Ok, we were running SEPM11. But we have now upgraded to sepm 12.1.1101.401.Strangely we are still getting the same problem..

Log.liveupdate below

17/10/2012, 11:55:02 GMT -> LiveUpdate flag value for this run is 0
17/10/2012, 11:55:02 GMT -> **** Starting a Silent LiveUpdate Session ****
17/10/2012, 11:55:02 GMT -> ***********************        Start of New LU Session        ***********************
17/10/2012, 11:55:02 GMT -> The command line is -S -S
17/10/2012, 11:55:02 GMT -> EVENT - SESSION START EVENT - The LiveUpdate session is running in Silent Mode.
17/10/2012, 11:55:02 GMT -> Check for updates to:  Product: LiveUpdate, Version: 3.3.2.2, Language: English.  Mini-TRI file name: liveupdate_3.3.2.2_english_livetri.zip
17/10/2012, 11:55:02 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantecliveupdate.com" URL: "http://liveupdate.symantecliveupdate.com" HostNumber: 0
17/10/2012, 11:55:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0 Downloading LiveUpdate catalog file
17/10/2012, 11:55:02 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.2.2_english_livetri.zip
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:02 GMT -> Progress Update: PRE_CONNECT: Proxy: "(not-available)" Agent: "Symantec LiveUpdate" AccessType: 0x0      
17/10/2012, 11:55:02 GMT -> Progress Update: CONNECTED: Proxy: "(not-available)" Agent: "1qcWdg1nJnQ0oQ1p7I7xDeQUDY0lpx+UAAAAAA" AccessType: 0x0      
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/liveupdate_3.3.2.2_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:02 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:02 GMT -> Download complete: Original estimated file size: 1663; Actual bytes downloaded: 1663
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantecliveupdate.com/liveupdate_3.3.2.2_english_livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip" HR: 0x0      
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:02 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:02 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:02 GMT -> LiveUpdate will check for Mini-TRI file support on the server since the first Mini-TRI file was not available (liveupdate_3.3.2.2_english_livetri.zip).
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:02 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:03 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:03 GMT -> Download complete: Original estimated file size: 1636; Actual bytes downloaded: 1636
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1 Downloading LiveUpdate catalog file
17/10/2012, 11:55:03 GMT -> LiveUpdate could not find the MiniTri.flg file on the server.  LiveUpdate is entering legacy mode and will attempt to download the full LiveUpdate Catalog file.
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:03 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:03 GMT -> Download complete: Original estimated file size: 1636; Actual bytes downloaded: 1636
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantecliveupdate.com/livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip contains HTML/DOCTYPE. It is invalid Tri file , and has been removed
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
17/10/2012, 11:55:03 GMT -> EVENT - SERVER SELECTION SUCCESSFUL EVENT - LiveUpdate connected to server liveupdate.symantecliveupdate.com at path  via a HTTP connection. The server connection connected with a return code of 1800, Success
17/10/2012, 11:55:03 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantec.com" URL: "http://liveupdate.symantec.com" HostNumber: 1
17/10/2012, 11:55:03 GMT -> Progress Update: DISCONNECT
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0 Downloading LiveUpdate catalog file
17/10/2012, 11:55:03 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.2.2_english_livetri.zip
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:03 GMT -> Progress Update: PRE_CONNECT: Proxy: "(not-available)" Agent: "1qcWdg1nJnQ0oQ1p7I7xDeQUDY0lpx+UAAAAAA" AccessType: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: CONNECTED: Proxy: "(not-available)" Agent: "1qcWdg1nJnQ0oQ1p7I7xDeQUDY0lpx+UAAAAAA" AccessType: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/liveupdate_3.3.2.2_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:03 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:03 GMT -> Download complete: Original estimated file size: 1619; Actual bytes downloaded: 1619
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantec.com/liveupdate_3.3.2.2_english_livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip" HR: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:03 GMT -> LiveUpdate will check for Mini-TRI file support on the server since the first Mini-TRI file was not available (liveupdate_3.3.2.2_english_livetri.zip).
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/minitri.flg", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:03 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:03 GMT -> Download complete: Original estimated file size: 1592; Actual bytes downloaded: 1592
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantec.com/minitri.flg", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1 Downloading LiveUpdate catalog file
17/10/2012, 11:55:03 GMT -> LiveUpdate could not find the MiniTri.flg file on the server.  LiveUpdate is entering legacy mode and will attempt to download the full LiveUpdate Catalog file.
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:03 GMT -> HttpSendRequest (status 200): Request succeeded
17/10/2012, 11:55:03 GMT -> Download complete: Original estimated file size: 1592; Actual bytes downloaded: 1592
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "http://liveupdate.symantec.com/livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:03 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip contains HTML/DOCTYPE. It is invalid Tri file , and has been removed
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
17/10/2012, 11:55:03 GMT -> EVENT - SERVER SELECTION SUCCESSFUL EVENT - LiveUpdate connected to server liveupdate.symantec.com at path  via a HTTP connection. The server connection connected with a return code of 1800, Success
17/10/2012, 11:55:03 GMT -> Progress Update: TRYING_HOST: HostName: "update.symantec.com" URL: "ftp://update.symantec.com/opt/content/onramp" HostNumber: 2
17/10/2012, 11:55:03 GMT -> Progress Update: DISCONNECT
17/10/2012, 11:55:03 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0 Downloading LiveUpdate catalog file
17/10/2012, 11:55:03 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.2.2_english_livetri.zip
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:03 GMT -> Progress Update: PRE_CONNECT: Proxy: "(not-available)" Agent: "1qcWdg1nJnQ0oQ1p7I7xDeQUDY0lpx+UAAAAAA" AccessType: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: CONNECTED: Proxy: "(not-available)" Agent: "1qcWdg1nJnQ0oQ1p7I7xDeQUDY0lpx+UAAAAAA" AccessType: 0x0      
17/10/2012, 11:55:03 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/liveupdate_3.3.2.2_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:04 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/liveupdate_3.3.2.2_english_livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip" HR: 0x0      
17/10/2012, 11:55:04 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:04 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:04 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\liveupdate_3.3.2.2_english_livetri.zip contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:04 GMT -> LiveUpdate will check for Mini-TRI file support on the server since the first Mini-TRI file was not available (liveupdate_3.3.2.2_english_livetri.zip).
17/10/2012, 11:55:04 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:04 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/minitri.flg", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/minitri.flg", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x0      
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:05 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:05 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
17/10/2012, 11:55:05 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
17/10/2012, 11:55:05 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1 Downloading LiveUpdate catalog file
17/10/2012, 11:55:05 GMT -> LiveUpdate could not find the MiniTri.flg file on the server.  LiveUpdate is entering legacy mode and will attempt to download the full LiveUpdate Catalog file.
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/livetri.zip", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/livetri.zip", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x0      
17/10/2012, 11:55:05 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
17/10/2012, 11:55:05 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
17/10/2012, 11:55:05 GMT -> C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\livetri.zip contains HTML/DOCTYPE. It is invalid Tri file , and has been removed
17/10/2012, 11:55:05 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
17/10/2012, 11:55:05 GMT -> EVENT - SERVER SELECTION SUCCESSFUL EVENT - LiveUpdate connected to server update.symantec.com at path /opt/content/onramp via a FTP connection. The server connection connected with a return code of 1800, Success
17/10/2012, 11:55:05 GMT -> Progress Update: HOST_SELECTION_ERROR: Error: 0x802A0027
17/10/2012, 11:55:05 GMT -> LiveUpdate did not find any new updates for the given products.
17/10/2012, 11:55:05 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Silent Mode. LiveUpdate found 0 updates available, of which 0 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
17/10/2012, 11:55:05 GMT -> IE6 support.
17/10/2012, 11:55:05 GMT -> ***********************           End of LU Session  

check this link, if it does not help pass on log.liveupdate.,

https://www-secure.symantec.com/connect/forums/sepm-liveupdate-has-error-liveupdate-encountered-one-or-more-errors-return-code-4

Possible Causes: Legacy proxy settings in the registry still persist after environmental changes on client machine.

Solution

The legacy proxy settings can be removed by performing the following steps:

1.   Open the registry (Start->Run->type "regedit").

2.  Go to HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings\connections

3.  Delete the registry keys "DefaultConnectionSettings" and "SavedLegacySettings".

4.  Reboot the machine.

Note:  These registry keys will automatically regenerate after reboot of machine.

Also, this also could be caused due to incorrect proxy server information in the following registry location: HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings

Removing the incorrect proxy info from this key and then rebooting allowed the client to communicate normally.

One important thing to keep in mind is that any incorrect proxy information must also be removed from the following two locations as well:

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\SavedLegacySettings

If the settings are not removed from these two keys, they will repopulate the Internet Settings key after every reboot.

Remove the incorrect proxy information from all 3 registry locations noted above, then reboot.

Just to add, in many of my cases, where was an issue with the System Account at User Proxy Level. They had to Bypass the Proxy on the server.

https://www-secure.symantec.com/connect/forums/liveupdate-returned-non-critical-error-3

Error: "LU1814: LiveUpdate could not retrieve the update list" (Enterprise)

http://www.symantec.com/business/support/index?page=content&id=TECH101808&locale=en_US

https://www-secure.symantec.com/connect/forums/problem-live-update-1

Ok, Thanks for this.... I have now had some success. Everything has now updated EXCEPT the Virus Definitions for v11 (v12 has updated). See below....

Virus and Spyware definitions Win32 11.0 10/02/2012 r1  02 October 2012 17:10:26 BST
Virus and Spyware definitions Win32 12.1 10/16/2012 r21  17 October 2012 13:45:30 BST
Virus and Spyware definitions Win64 11.0 10/02/2012 r1  02 October 2012 17:02:32 BST
Virus and Spyware definitions Win64 12.1 10/16/2012 r21  17 October 2012 13:42:27 BST          

Now when I run Liveupdate it is showing everything as "up to date". However, the V11 definitions clearly are not?

HI,

Can you check your sepm server up to date or not ?

also check sep client update or not ?

Not sure what you mean....

The paste in the last post was directly from SEPM12, admin, servers, local site, show liveupdate downloads.

This is showing EVERYTHING up to date EXCEPT WIN32/64 11.0

The SEPM 12 Home page is showing....

The endpoints are showing up to date... but this is only because while we had issues with the server, we directed them to get updates directly from the internet.

Looking at the "download time" entries next to your v11 definitions, the SEPM doesn't appear to be even trying to grab the v11 defs anymore, not since 2nd October anyway.

Does this date co-incide with when you upgraded your SEPM by any chance?  I've checked on our own v12.1RU1MP1 SEPM and can confirm the v11 defs entry is not on our LiveUpdate Downloads list (see screenie), and also that our SEPM is correctly updating v11 clients.

I suspect these may no longer necessary...

In which case... we may have another issue now then. If the Server has up to date definitions, then we have no clients requesting definitions (I can tell this by virtually 0% network traffic).

The online clients are showing on the server as green dots. But the clients are not showing green dots? Does this mean we have a communication issue? 

HI,

Check windows firewall should be off ?

UAC are disabled or not ?

Symantec Endpoint Protection Manager (SEPM) 12.1 is not updating 32 or 64 bit virus definitions

http://www.symantec.com/business/support/index?page=content&id=TECH166923

In this case, check if the clients are connecting to the SEPM properly, check these Articles:

Symantec Endpoint Protection Manager 12.1 Communication Troubleshooting

http://www.symantec.com/docs/TECH160964

Troubleshooting communication problems between the management server and the client

http://www.symantec.com/docs/HOWTO55017

Then, Troubleshoot the Liveupdate Issue, check this Article:

Symantec Endpoint Protection: LiveUpdate Troubleshooting Flowchart

http://www.symantec.com/docs/TECH95790

HI,

Did you received your answer ?

If you have received your answer please don't forgot mark as solution