Endpoint Protection

 View Only
Expand all | Collapse all

Outdated reply protocol

Migration User

Migration UserAug 22, 2011 07:14 PM

  • 1.  Outdated reply protocol

    Posted Aug 21, 2011 07:13 AM

    My Symantec 10.2 build#276 Antivirus updates periodically, but I receive a message that it reports back to Symantec in an outdated format. Can my existing program be fixed? Thank you.



  • 2.  RE: Outdated reply protocol

    Posted Aug 22, 2011 04:55 AM

    Hi ITD,

    I am not sure what message you are receiving.  Can you add the exact text of the message to this thread? 

    Also: if your version of SAV is 10.2.0.276, then you are running the very first release of SAV for Vista.  It came out about foura and a half years ago: I very strongly recommend that you upgrade!  The latest release in that product line is SAV 10.2 MR4 (SAV 10.2.4.4000).  Upgrading to MR4 will give you greater stability and security. 

    (You can of course also upgrade to SEP 11 or SEP 12, which add even greater features....)

    Hope this helps!

    Thanks and best regards,

    Mick



  • 3.  RE: Outdated reply protocol

    Posted Aug 22, 2011 06:11 AM

    Mr. Mick2009,  Thank you for the advice to upgrade. I believe 10.2.0.276 is exactly what  I have, and I'll verify that soon. I believe the message that SAV reports back in an obsolete format comes from windows7 but I'll make notes the next time the message appears. Windows also recommended update. I know your time is valuable so I'll check the facts.



  • 4.  RE: Outdated reply protocol

    Posted Aug 22, 2011 06:28 AM

    One thing to bear in mind: SAV 10.2 was invented before Windows 7.  It was not tested and certified on that platform.  It is supported on Vista and Windows Server 2008, but not designed for Win7 specifically.

    I will continue to monitor this thread! 

    Many thanks, ITD!

    Mick



  • 5.  RE: Outdated reply protocol

    Posted Aug 22, 2011 06:46 AM

    Mr. Mick2009, you seem to be awake, so I'll standby.  SAV 10.2.0.276 is my program. When it updates, it reports >AvengeMicroDefs25 SAV Corp 2.5, >Live Update, and >SAV Corp Client as being installed and running. When windows tries to install the new files; it stalls at 99%, and eventually quits. A flag appears with the message: "check anti virus options". Windows on-line diagnostics made a statement to the effect that SAV had not been updated often enough, and was left behind by a language change. I like my version of SAV, and will standby.



  • 6.  RE: Outdated reply protocol

    Posted Aug 22, 2011 07:44 AM

    Hi ITD,

    Is the "outdated" message from Windows Security Center or from SAV 10 itself?

    If it is from Windows, that will probably be fixed by installing SAV 10.2 MR4.  There was a known issue.

    See the following article:

    Status of Symantec Endpoint Protection (SEP) or Symantec Antivirus (SAV) 10.2 components is no longer correctly represented in Windows Security Center
    Article: TECH96174
    Article URL http://www.symantec.com/docs/TECH96174 
     

    If the SAV client is failing to update its definitions, can you locate the log.liveupdate and attach it to this thread?

    Thanks again,

    Mick



  • 7.  RE: Outdated reply protocol

    Posted Aug 22, 2011 05:53 PM

    Hi Mick, SAV is usually invisible, my messages come from windows. The messages started after I downloaded some "free" software to open pdf files, and open .dll files for updating BIOS. I suspect that I wrecked my own machine. I will read  /TECH96174, and look for log.liveupdate. Thank you for the tutoring.



  • 8.  RE: Outdated reply protocol

    Posted Aug 22, 2011 07:14 PM

    Mr Mick, I'm doing my best.



  • 9.  RE: Outdated reply protocol

    Posted Aug 23, 2011 08:15 PM
      |   view attached

    Mr. Mick2009, YES I SHOULD UPGRADE!...but then I won't know if I wrecked SAV or if SAV's subscription ran out. You can tell me, right?

    Attachment(s)

    zip
    log.liveupdate_0.zip   991 B 1 version


  • 10.  RE: Outdated reply protocol

    Posted Aug 24, 2011 04:30 AM

    On a Windows Vista computer, log.liveupdate can be found in :

    c:\ProgramData\symantec\liveupdate\Log.LiveUpdate

    NOTE: The ProgramData folder is a hidden folder.
     



  • 11.  RE: Outdated reply protocol

    Posted Aug 24, 2011 06:24 AM

    Mr. Mike, My first attempt at attaching Log.LiveUpdate was rejected without comment. The second attempt allowed to send my search for the file. The third attempt was disallowed by your file attachment restrictions. I tried zipping Log.LiveUpDate but Windows won't allow it. The file(?) is about one megabyte, and it's doing OK. I was afraid I had erased it when I attempted to attach it. I haven't given up on attaching the file but I am proceeding with caution.



  • 12.  RE: Outdated reply protocol

    Posted Aug 24, 2011 06:58 AM
      |   view attached

    Mr. Mike , Windows made things challenging, but I think log.liveupdate is now attached. Windows allowed me to make a copy in documents and zip the copy, but it would not allow anything else. There were many warnings not to touch it.

    Attachment(s)

    zip
    Log (2).zip   61 KB 1 version


  • 13.  RE: Outdated reply protocol
    Best Answer

    Posted Aug 24, 2011 07:54 AM

    Hi ITD,

    That log indicates that your SAV 10.2 client is updating correctly.  Here's text from the last three sessions:

    8/20/2011, 6:59:53 GMT -> EVENT - PRODUCT UPDATE SUCCEEDED EVENT - Update available for Avenge MicroDefs25 SavCorp10.2 - MicroDefsB.CurDefs - SymAllLanguages. Update for CurDefs takes product from update 110805003 to 110819007...... The Update executed with a result code of 1800, => Success

    8/20/2011, 6:59:53 GMT -> EVENT - PRODUCT UPDATE SUCCEEDED EVENT - Update available for Avenge MicroDefs25 SavCorp10.2 - MicroDefsB.Jul - SymAllLanguages. Update for HubDefs takes product from update 110719022 to 110818021. ..... The Update executed with a result code of 1800, => Success

    8/20/2011, 6:59:53 GMT -> EVENT - SESSION END SUCCESSFUL EVENT - The LiveUpdate session ran in Silent Mode. LiveUpdate found 2 updates available, of which 2 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1800, Success

    8/21/2011, 9:44:16 GMT -> EVENT - PRODUCT UPDATE SUCCEEDED EVENT - Update available for Avenge MicroDefs25 SavCorp10.2 - MicroDefsB.CurDefs - SymAllLanguages. Update for CurDefs takes product from update 110819007 to 110820005..... The Update executed with a result code of 1800, => Success

    8/21/2011, 9:44:16 GMT -> EVENT - SESSION END SUCCESSFUL EVENT - The LiveUpdate session ran in Express Mode. LiveUpdate found 1 updates available, of which 1 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1800, Success

    8/22/2011, 10:16:54 GMT -> EVENT - PRODUCT UPDATE SUCCEEDED EVENT - Update available for Avenge MicroDefs25 SavCorp10.2 - MicroDefsB.CurDefs - SymAllLanguages. Update for CurDefs takes product from update 110819007 to 110821003. ..... The Update executed with a result code of 1800, => Success

    8/22/2011, 10:16:54 GMT -> EVENT - SESSION END SUCCESSFUL EVENT - The LiveUpdate session ran in Express Mode. LiveUpdate found 1 updates available, of which 1 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1800, Success

    Everything there is normal and successful! &: )

    I do recommend upgrading to SAV 10.2 MR4 to resolve the Security Center issue, but you can consider the message you are seeing there as cosmetic.  SAV is staying up-to-date.

    Please update this forum thread with anything else you need, or mark it "solved" if this has answered your question! &: ) 

    All the best,

    Mick