Endpoint Protection

 View Only

  • 1.  Replication not woking after upgrading to SEPM 12.1.2

    Posted Jul 25, 2013 01:45 AM

    HI,

    I have 3 SEPM servers in my office (2 at same location and 1 at remote location). Few days back i have upgraded  all SEPM server to 12.1.2 from 11.06.

    While upgrade i have deleted the replication between all 3 servers and after upgrade the replication is enabled back. But now the replication is not proper. Client count in all 3 SEPM is not matching. Sometime replication fails.

     

    Help me with this.



  • 2.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Posted Jul 25, 2013 01:50 AM

    can you post the scm-server0.log

    and also check this document

    Unable to connect to the server specified" error during the replication of Symantec Endpoint Protection Manager

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



  • 3.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Posted Jul 25, 2013 01:50 AM

    hi,

    Can you provide scm.server.log & Replication.log ?

     

    "Unable to connect to the server specified" error during the replication of Symantec Endpoint Protection Manager

    Article:TECH106224  |  Created: 2008-01-13  |  Updated: 2011-11-29  |  Article URL http://www.symantec.com/docs/TECH106224

     



  • 4.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Broadcom Employee
    Posted Jul 25, 2013 01:50 AM

    you need to add replication partner again

    http://symantec.com/docs/TECH104986



  • 5.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Broadcom Employee
    Posted Jul 25, 2013 01:52 AM

    what is the error message?

    can you post the scm-server-0.log after replication event?



  • 6.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Posted Jul 25, 2013 03:15 AM
      |   view attached

    Hi Pete,

    Replication partner is added. Attached the replication settings screen shot.

    Also i have attached the server log file.

    To brief on my settings  -

    All 3 server will replicate each other. Now while replicating it will stop at 10% or finish or it will fail.

    Replication is scheduled for every hour. Earlier it was auto and i changed it to just check.

    Attachment(s)

    zip
    logs_and_Screenshot.zip   330 KB 1 version


  • 7.  RE: Replication not woking after upgrading to SEPM 12.1.2

    Broadcom Employee
    Posted Jul 25, 2013 10:04 AM

    Hello,

    Thank you for posting in Symantec community.

    I would be glad to answer your query.

    Had been ever replication successful after an upgrade to SEP 12.1 RU2?

    Could you please attach replication logs.

    C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\Logs

    The ReplicationLocal-0.log contains Replication events initiated from the Local SEPM and the ReplicationRemote-0. log contains events received from the Replication partner

    Also could you please try these steps

    Add to the following to the conf.prop on all the SEPMs

    scm.replication.keepalive=1

    Reboot, Test, If that fails

    Change scm.replication.keepalive=10 in the conf.properties file

    Followings are the fixes

    in SEP 12.1 RU3, do you see this error message?

    1) Replication fails with a Java error: "GC overhead limit exceeded"

    Fix ID: 2920217/3055586

    Symptom: After upgrading to Symantec Endpoint Protection Manager 12.1.2, replication fails with the exception message "OutOfMemoryError: GC overhead limit exceeded."

    Solution: Modified the replication function to avoid a scenario where object references could be recursively checked.

     2) Replication failed

    Fix ID: 2810324

    Symptom: The replication fails continuously. The data.zip file is generated and transferred, but replication is not successful.

    Solution: Fixed this issue by cloning the default management server list in the Enforcer's policy.

     

    SEP 12.1 RU2 MP1 has also one fix related to replication, here it is.

    AgentSweepingTask fails to clean the SEM_CONTENT table, leading to replication issues
     
    Fix ID: 2956524
     
    Symptom: Symantec Endpoint Protection Manager replication fails, and the AgentSweepingTask logs contain reported deadlocks. Multiple applications or processes attempting to access the database at the same time appear to trigger these deadlocks.
    Solution: Added additional retries and failsafes to ensure that the AgentSweepingTask is given a higher priority in the event of multiple failures and failed retries to ensure it can run.

    I hope you have performed system reboot after the SEPM upgrade.