Symantec SEP 11 Manager is not getting updates from the Internet. It can access akamai, and Liveupdate states that all the prducts are up to date, but it is not. The manager does show that there are new updates, but Liveupdate says all the products are up to date. I would like to know how this is possible.

You will get all the info on the picture.

Snap shot missing ?

Does you have try to manually update SEPM

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

Screen print attached

Have you tried updating with the JDB file?

I did update it with JDB, but I am not going to do it everyday

What database are you using ?

If you are using SQL please check below articles.

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

Post the log.liveupdate file from the SEPM as it should show what's going on

2014/01/22, 06:58:02 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:02 GMT -> The PreSession callback for product SESM Content Catalog completed with a result of 0x0       
2014/01/22, 06:58:02 GMT -> Progress Update: TRYING_HOST: HostName: "C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU\CONTENT.ZIP0001" URL: "C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU\CONTENT.ZIP0001" HostNumber: 0
2014/01/22, 06:58:02 GMT -> In TempHostEx mode, LiveUpdate will retrieve updates from this location: C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU\CONTENT.ZIP0001
2014/01/22, 06:58:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
2014/01/22, 06:58:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0    Downloading Mini-TRI files
2014/01/22, 06:58:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
2014/01/22, 06:58:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1    Downloading LiveUpdate catalog file
2014/01/22, 06:58:02 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.
2014/01/22, 06:58:02 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
2014/01/22, 06:58:02 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU\CONTENT.ZIP0001\livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
2014/01/22, 06:58:02 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU\CONTENT.ZIP0001\livetri.zip", Full Download Path: "(null)" HR: 0x802A0017
2014/01/22, 06:58:02 GMT -> HR 0x802A0017 DECODE: E_UNABLE_TO_CONNECT_TO_NETWORK_RESOURCE
2014/01/22, 06:58:02 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
2014/01/22, 06:58:02 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
2014/01/22, 06:58:02 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server C:\PROGRAM FILES (X86)\SYMANTEC\SYMANTEC ENDPOINT PROTECTION\SMCLU at path C:\PROGRAM%20FILES%20(X86)\SYMANTEC\SYMANTEC%20ENDPOINT%20PROTECTION\SMCLU\CONTENT.ZIP0001 via a LAN connection. The server connection attempt failed with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
2014/01/22, 06:58:02 GMT -> Progress Update: HOST_SELECTION_ERROR: Error: 0x802A0027
2014/01/22, 06:58:02 GMT -> LiveUpdate did not find any new updates for the given products.
2014/01/22, 06:58:02 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.
2014/01/22, 06:58:02 GMT -> IE9 support.
2014/01/22, 06:58:02 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Content Catalog.
2014/01/22, 06:58:02 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:02 GMT -> The PostSession callback for product SESM Content Catalog completed with a result of 0x0       
2014/01/22, 06:58:02 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
2014/01/22, 06:58:02 GMT -> ProductRegCom/luProductReg(PID=6084/TID=7620): Destroyed luProductReg object.
2014/01/22, 06:58:02 GMT -> LiveUpdate has called the last callback for product SESM Content Catalog, so LiveUpdate is informing the callback proxy that it can exit.
2014/01/22, 06:58:02 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win32 with moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264}.
2014/01/22, 06:58:02 GMT -> The callback proxy executable for product {7073FE74-CAB0-42cc-B839-9808FCB47909} is exiting with no errors
2014/01/22, 06:58:02 GMT -> The callback proxy for moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} was successfully registered with LiveUpdate.
2014/01/22, 06:58:02 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win32.
2014/01/22, 06:58:02 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win32.
2014/01/22, 06:58:04 GMT -> ProductRegCom/luProductReg(PID=6344/TID=6064): Successfully created an instance of an luProductReg object!
2014/01/22, 06:58:04 GMT -> ProductRegCom/luProductReg(PID=6344/TID=6064): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
2014/01/22, 06:58:04 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:04 GMT -> The PostSession callback for product SESM AntiVirus Client Win32 completed with a result of 0x0       
2014/01/22, 06:58:04 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
2014/01/22, 06:58:04 GMT -> ProductRegCom/luProductReg(PID=6344/TID=6064): Destroyed luProductReg object.
2014/01/22, 06:58:04 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
2014/01/22, 06:58:04 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win64 with moniker {E4052532-F65C-4007-B620-DBEE893C2B2A}.
2014/01/22, 06:58:04 GMT -> The callback proxy executable for product {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} is exiting with no errors
2014/01/22, 06:58:04 GMT -> The callback proxy for moniker {E4052532-F65C-4007-B620-DBEE893C2B2A} was successfully registered with LiveUpdate.
2014/01/22, 06:58:04 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win64.
2014/01/22, 06:58:04 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win64.
2014/01/22, 06:58:06 GMT -> ProductRegCom/luProductReg(PID=3924/TID=2964): Successfully created an instance of an luProductReg object!
2014/01/22, 06:58:06 GMT -> ProductRegCom/luProductReg(PID=3924/TID=2964): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
2014/01/22, 06:58:06 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:06 GMT -> The PostSession callback for product SESM AntiVirus Client Win64 completed with a result of 0x0       
2014/01/22, 06:58:06 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
2014/01/22, 06:58:06 GMT -> ProductRegCom/luProductReg(PID=3924/TID=2964): Destroyed luProductReg object.
2014/01/22, 06:58:06 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
2014/01/22, 06:58:06 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Network Access Control Client Win32 with moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE}.
2014/01/22, 06:58:06 GMT -> The callback proxy executable for product {E4052532-F65C-4007-B620-DBEE893C2B2A} is exiting with no errors
2014/01/22, 06:58:06 GMT -> The callback proxy for moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE} was successfully registered with LiveUpdate.
2014/01/22, 06:58:06 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win32.
2014/01/22, 06:58:06 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win32.
2014/01/22, 06:58:08 GMT -> ProductRegCom/luProductReg(PID=7876/TID=7600): Successfully created an instance of an luProductReg object!
2014/01/22, 06:58:08 GMT -> ProductRegCom/luProductReg(PID=7876/TID=7600): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
2014/01/22, 06:58:08 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:08 GMT -> The PostSession callback for product SESM Network Access Control Client Win32 completed with a result of 0x0       
2014/01/22, 06:58:08 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
2014/01/22, 06:58:08 GMT -> ProductRegCom/luProductReg(PID=7876/TID=7600): Destroyed luProductReg object.
2014/01/22, 06:58:08 GMT -> LiveUpdate has called the last callback for product SESM Network Access Control Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
2014/01/22, 06:58:08 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Network Access Control Client Win64 with moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26}.
2014/01/22, 06:58:08 GMT -> The callback proxy executable for product {A6BA2770-E351-4694-AB02-5358E0F9CDBE} is exiting with no errors
2014/01/22, 06:58:08 GMT -> The callback proxy for moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26} was successfully registered with LiveUpdate.
2014/01/22, 06:58:08 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win64.
2014/01/22, 06:58:08 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win64.
2014/01/22, 06:58:10 GMT -> ProductRegCom/luProductReg(PID=8032/TID=4976): Successfully created an instance of an luProductReg object!
2014/01/22, 06:58:10 GMT -> ProductRegCom/luProductReg(PID=8032/TID=4976): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
2014/01/22, 06:58:10 GMT -> The callback proxy finished executing the callback with a result code of 0x0
2014/01/22, 06:58:10 GMT -> The PostSession callback for product SESM Network Access Control Client Win64 completed with a result of 0x0       
2014/01/22, 06:58:10 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
2014/01/22, 06:58:10 GMT -> ProductRegCom/luProductReg(PID=8032/TID=4976): Destroyed luProductReg object.
2014/01/22, 06:58:10 GMT -> LiveUpdate has called the last callback for product SESM Network Access Control Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
2014/01/22, 06:58:10 GMT -> The callback proxy executable for product {C6ACF447-A89C-42d7-A954-E31003AE0B26} is exiting with no errors

SQL, but that is not the issue. Liveupdate is running through, and it seems like it is not getting the latest definition information from Akamai. In the logs you will find the error "could not connect to network resource", but why is liveupdate connecting when executed manually. 

I will see tomorrow if the updates go through, but it seems like it is not getting info from Akamai.

See this articles

A LiveUpdate session run within the Symantec Endpoint Protection Manager fails with error LU1814

Also try to uninstall live update and reinstall

How to Uninstall and Reinstall LiveUpdate When a Symantec Endpoint Protection Manager or Symantec Endpoint Protection Client is Installed (SEP 11.x)

LU failed to retrieve some updates, when did this issue start?

Do you havea proxy? If SEPM correctly configured to go thru it? When did this issue start?

The SEP managers are bypassing the proxy. All is set to not to use a proxy. It started since the Akamai address changed (2 days ago), and we changed it on the firewall also. I thought it could be a firewall issue, but if I run LUALL it connects to the internet and states that all the products are up to date.

We can not install or reinstall anything without a change, and it takes weeks to get it approved, so I will see tomorrow morning if it goes through.

Thanks Brian/James, I will keep you updated

You can review this article:

How to determine whether your firewall is blocking LiveUpdate

Have you checked that you have not exceeded the Autogrowth size of your SEPM database?

It is a very common error.

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

Did you need more help here ?

Hi GJCronje,

This is not a Correct Solution,Please Update any above comments which best help you.

Please select the correct solution as already suggested

Hi

There is not really a solution here. The updates on the certain akamai server was late and SEP never got updated.

Nothing was wrong with proxy or database.