Live update is not working..SEPM 12.1.67.4971

Created: 04 Jan 2013 | Updated: 04 Jan 2013 | 4 comments

jijithp

Dear Team, I am facing one issue with SEPM liveuupdate: When i am trying to update the SEPM server getting the below mentioned messages.My current Virus definition is given below Windows Definitions Latest from Symantec: 01/03/2013 r32 Latest on Manager: 12/09/2012 r6 Message Getting after running Live update is as follows.. anuary 4, 2013 2:10:21 PM IST: LiveUpdate succeeded. [Site: PINSAV02] [Server: PINSAV02] January 4, 2013 2:10:21 PM IST: LUALL.EXE finished running. [Site: PINSAV02] [Server: PINSAV02] January 4, 2013 2:10:21 PM IST: LUALL.EXE successfully updated the content. Return code = 0. [Site: PINSAV02] [Server: PINSAV02] January 4, 2013 2:10:18 PM IST: No updates found for Symantec Endpoint Protection Win64 12.1 (English). [Site: PINSAV02] [Server: PINSAV02]

Discussion Filed Under:

Security, Endpoint Protection (AntiVirus)

Login or register to post comments
Comments RSS Feed

Comments 4 Comments • Jump to latest comment

Ashish-Sharma

Live update is not working..SEPM 12.1.67.4971 - Comment:04 Jan 2013 : Link

hi,

Can you pass log.liveupdate logs

The SEPM does not update virus definitions. Liveupdate not working on the Symantec Endpoint Protection Manager 12.1

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

https://www-secure.symantec.com/connect/articles/t...

Duplicated Thread:

https://www-secure.symantec.com/connect/forums/liv...

Thanks In Advance

Ashish Sharma

SEPM Knowledgebase Documents

pete_4u2002 Symantec Employee

Live update is not working..SEPM 12.1.67.4971 - Comment:04 Jan 2013 : Link

check if this link helps
http://www.symantec.com/docs/TECH166923

Cheers!
Pete

Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619

SMLatCST Partner Accredited

Live update is not working..SEPM 12.1.67.4971 - Comment:04 Jan 2013 : Link

Generally speaking, when the SEPM's LU encounters a problem, it will return some sort of error code. For it to produce "Return code = 0" seems to suggest that the SEPM thinks it ran correctly.

This is usually down to the SEPM using a proxy to access the Internet, and that proxy (e.g. ISA) is configured to cache web content. Does this apply to your environment by any chance? If so, you may want to get test by disabling caching (http://support.microsoft.com/kb/837352)

http://www.cstl.com/