Endpoint Protection

 View Only
Expand all | Collapse all

SEP 11.0.7 can't update virus definition from SEP12.1.4

  • 1.  SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 29, 2014 11:35 PM

    Dear All,

    I have a problem about SEP 11.0.7 can't update virus definition from SEP12.1.4.

    Prevously, I use the SEP 11.0.7 and I upgraded to SEP 12.1.4.

    The clients 70% still use 11.0.7 and 30% has upgraded to 12.1.4.

    I have problem only version 11.0.7 but SEP 12.1.4 can update normally.

    SEPM has normally update. I test by move client version 11.0.7 to other SEPM, it's can to update virus definition.

    (I have 2 SEPM cluster.[DC and DR])

    I'm so confuse.

     

    Thanks. 



  • 2.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 29, 2014 11:38 PM
    Enable sylink debugging and let it run thru a few heartbeats, post the log here for review.


  • 3.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 03:34 AM
      |   view attached

    Hi _Brian

    The log file in attachment.

    Thanks.

    Attachment(s)

    zip
    Sylink.log__0.zip   20 KB 1 version


  • 4.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 03:38 AM

    Does SEP client showing online ? Try to replace sylink.xml one client and check again .



  • 5.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 05:38 AM

    Check this document, check if you have any inactive connection setting in IE..

    SEP client is not able to communicate with SEPM

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



  • 6.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 06:38 AM

    Yes, client online normally. Have latest check time to SEPM today.



  • 7.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 06:54 AM

    Is it possible that the two different SEPM sites are configured differently in what content they download and distribute?

    If everything else for these v11RU7 clients is working fine (policies, group changes, log uploads, etc), then I'd be inclined to check out the Platform and Language choices on the SEPM in the below lcoation:

    ADMIN -> Servers -> highlight "Local Site" -> Click "Edit Site Properties" -> LiveUpdate tab



  • 8.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jun 30, 2014 10:47 AM

    According to your logs. Check the thread solution

    https://www-secure.symantec.com/connect/forums/sep-client-sepm-does-not-get-updates



  • 9.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jul 01, 2014 09:39 AM

    On sylink debug log show "<mfn_LiveUpdate> EVENT_LU_REQUIRE_STATUS returned ERROR_SYSTEM_UNKNOWN - Ignore LU content. Moniker: {D6AEBC07-D833-485f-9723-6C908D37F806} Seq:140612012"



  • 10.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jul 01, 2014 09:52 AM

    May or may not be the issue, see here:

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

    Any other errors showing?



  • 11.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jul 01, 2014 09:55 AM

    Have you Try to replace sylink.xml one client ?



  • 12.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Jul 01, 2014 10:08 AM

    Personally, I'd like to see the sylink logs from this same client when connected to the DR SEPM that is successfully delivering content to these SEP11RU7MP3 clients to compare the results.

    If identically configured, both SEPMs should be offering the same content under the same GUID/monikers, meaning the client will receive the same list.  It'd be interesting to see what differences come out of the logs.

    On a slightly less technical view though, have you tried the usual repair/reinstall processes on a SEP11 client yet?



  • 13.  RE: SEP 11.0.7 can't update virus definition from SEP12.1.4

    Posted Sep 15, 2014 08:56 PM

    Thanks everyone. This problem has been solved by itself. I wake up on this day and it work properly.

    So surprise !!