Video Screencast Help

LiveUpdate unable to update the Virus and Antispyware protection definitions

Created: 19 Oct 2007 • Updated: 21 May 2010 | 8 comments
HN(PT)'s picture
Hello
 
Can some one help please
 
After unistall (removed) the RC of Symantec Endpoint Protection, and after INSTALL the new version and final Symantec Endpoint Protection, my liveupdate (continue) to go to the old beta live update server , and can't update the new version of the EP.
 
Actual versions installed on MS Vista are:
 
v11.0.780.1109 for Symantec Endpoint Protection
v3.3.0.61 for LiveUpdate
 
Many thanks in advanced
 
Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Russ H's picture

If this is a managed solution, is the client still hooked up to a Beta SEPM? If so, try upgrading your SEPM to the RC (a Beta SEPM might be pushing a configuration to the SEP telling it to get it's updates from the beta server).

 

If this is an unmanaged solution, and if SEP and LiveUpdate are only Symantec products that are installed, try uninstalling both SEP and LiveUpdate. Then install SEP again.

HN(PT)'s picture
Hello Russ H
 
It's not managed, is single install on my PC, and i already unistall SEP and liveUpdate, and make a new fresh install of SEP with LiveUpdate.
 
Did not work, LiveUpdate continue to connect to BETA Site!
 
Thanks anyway!
 
Rgds
Russ H's picture
It's possible that LiveUpdate didn't clean up during its uninstall (it's usually pretty good about this, but sometimes it's not) and this might be causing the beta connection settings to persist. If this is the case, after you uninstall LiveUpdate, go and delete the C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate directory (note: Application Data is a "hidden" directory, you'll have to enable explorer to show hidden files/directories to see it).
 
 
If that doesn't solve the problem, then SEP 11.0 is configuring LiveUpdate to point to the beta LiveUpdate server somehow (I don't know of another Symantec product that does this).
 
Question: How do you know it's connecting to the beta LiveUpdate server? Are you seeing this displayed in the interactive LiveUpdate screen? Are you looking in the Log.LiveUpdate (located in the aforementioned LiveUpdate directory).
 
 
rhoopes's picture


Russ H wrote:
 
Question: How do you know it's connecting to the beta LiveUpdate server? Are you seeing this displayed in the interactive LiveUpdate screen? Are you looking in the Log.LiveUpdate (located in the aforementioned LiveUpdate directory).
 
 



When LiveUpdate runs, a status is displayed on the screen with the following:

 
LiveUpdate Status
 
> Submission Control signatures
> Symantec Endpoint Protection client
> Symantec Security Software
> Symantec Shared Components
 
Initializing...
Connecting to Beta LiveUpdate Server...
Connecting to Beta LiveUpdate Server 2...
Unable to connect to host
 
I'm pretty sure that both SEP and LiveUpdate will have to be Uninstalled before a production version of SEP can be installed.  That or perhaps there is a "LiveUpdate Update" executable that can update the beta LiveUpdate and replace the link to the Beta LiveUpdate Servers?
Todd Fitkin's picture

Hi rhoopes,


Go into the Documents and Settings\All Users\Application Data\Symantec\LiveUpdate directory and delete the settings.liveupdate file, then try LiveUpdate again. LiveUpdate will repair the missing file with a default settings file, pointing it back to the production LiveUpdate servers.

Thanks,

OJ

Todd Fitkin's picture

A couple more things of note:

1. Make a backup of the settings.liveupdate file before deletion "just in case".
2. If you uninstall LiveUpdate and plan on deleting any files, make sure you backup the product.inventory.liveupdate as this holds Symantec Endpoint Protections product information for LiveUpdate.

rhoopes's picture
OJ wrote:
Go into the Documents and Settings\All Users\Application Data\Symantec\LiveUpdate directory and delete the settings.liveupdate file, then try LiveUpdate again. LiveUpdate will repair the missing file with a default settings file, pointing it back to the production LiveUpdate servers.

That did the trick!  Thanks

Todd Fitkin's picture

Glad I could help. BTW: Russ H's suggestions would also have worked.