Video Screencast Help

SEPM Liveupdate has an error: LiveUpdate encountered one or more errors. Return code = 4

Created: 22 Mar 2011 • Updated: 05 Dec 2011 | 8 comments
This issue has been solved. See solution.

Recently installed the SEPM 11.0 but liveupdate can not download updates... it has the following error: LiveUpdate encountered one or more errors. Return code = 4

I have gone through most of the solutions on the forum but I can not  get it to work. Please assist, i have attached the Log.Liveupdate

Comments 8 CommentsJump to latest comment

w-d's picture

I found this error code in Log.LiveUpdate:

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.

It indicates the issue with the proxy. Please follow these documents:

Edwin_Mu's picture

Indeed we are using a prozy server.

I did all in the specfied documents but I am not getting the following error, and not the 1814 error:

HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.

w-d's picture

Can you check if launching manually LiveUpdate it gives the same errors?

If LiveUpdate is laumched automatically it uses the System account. When launched manually it uses the currently logged user.

Mithun Sanghavi's picture


Check SYSTEM account proxy settings through using a Scheduled Task

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Swapnil khare's picture

Hello Edwin ,

As stated above by Mithun this is a proxy issue .

Please try to Enable logs on your proxy and check them after a failed update for any requests related with Symantec LiveUpdate & then Create approriate rules for allowing the required connections.

Thank you

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Edwin_Mu's picture

I seem not to understand. THe updates were downloaded on wednedsay but now i still get the error.

Mithun Sanghavi's picture


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


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.

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Vikram Kumar-SAV to SEP's picture

Did you change any IE setting or change proxy setting ?

Vikram Kumar

Symantec Consultant

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