Endpoint Protection

Main Site and Partner Site both running version 11.0.4202 (MR4-MP2)

After initiating a replication from the main-site I receive an error on the partner-site, while trying to replicate.


20 August 2009 14:42:36:  Replication from remote site NEIT Central SEPM to local site Torbay Primary School finished unsuccessfully  [Site: Torbay Primary School]  [Server: tpfp01]
20 August 2009 14:42:35:  Unable to fetch changed data from remote site [NEIT Central SEPM]: JZ0BE: BatchUpdateException: Error occurred while executing batch statement: ASA Error -193: Primary key for table 'COMMAND' is not unique  [Site: Torbay Primary School]  [Server: tpfp01]
20 August 2009 14:42:07:  Replication data from remote site NEIT Central SEPM is received by local site Torbay Primary School  [Site: Torbay Primary School]  [Server: tpfp01]
20 August 2009 14:39:22:  Replication from remote site NEIT Central SEPM to local site Torbay Primary School being initiated  [Site: Torbay Primary School]  [Server: tpfp01]
20 August 2009 14:39:22:  Replication from remote site NEIT Central SEPM to local site Torbay Primary School finished unsuccessfully  [Site: Torbay Primary School]  [Server: tpfp01]


scm-server-0.log on partner site:

2009-08-20 14:42:35.781 SEVERE: Unknown Exception in: com.sygate.scm.server.replication.ReplicationTask
com.sybase.jdbc2.jdbc.SybBatchUpdateException: JZ0BE: BatchUpdateException: Error occurred while executing batch statement: ASA Error -193: Primary key for table 'COMMAND' is not unique
    at com.sybase.jdbc2.jdbc.ErrorMessage.raiseBatchUpdateException(ErrorMessage.java:991)
    at com.sybase.jdbc2.jdbc.SybStatement.batchLoop(SybStatement.java:1424)
    at com.sybase.jdbc2.jdbc.SybStatement.sendBatch(SybStatement.java:1227)
    at com.sybase.jdbc2.jdbc.SybStatement.executeBatch(SybStatement.java:1185)
    at com.sybase.jdbc2.jdbc.SybStatement.executeBatch(SybStatement.java:1101)
    at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeBatch(SybPreparedStatement.java:951)
    at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:294)
    at com.sygate.scm.server.replication.table.DefaultTableReplicator.batchExecute(DefaultTableReplicator.java:165)
    at com.sygate.scm.server.replication.table.DefaultTableReplicator.replicateTable(DefaultTableReplicator.java:148)
    at com.sygate.scm.server.replication.table.DefaultTableReplicator.replicateTable(DefaultTableReplicator.java:201)
    at com.sygate.scm.server.replication.ReplicationTask.replicateTableData(ReplicationTask.java:1290)
    at com.sygate.scm.server.replication.ReplicationTask.replicateTableData(ReplicationTask.java:1249)
    at com.sygate.scm.server.replication.ReplicationTask.processRelicationData(ReplicationTask.java:3065)
    at com.sygate.scm.server.replication.ReplicationTask.replicate(ReplicationTask.java:313)
    at com.sygate.scm.server.replication.ReplicationTask.run(ReplicationTask.java:248)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)

I have tried re-creating the partners on both sites, and deleting and reestablishing the partner-site database.
Also clearing out the inbox/outbox in the Replication folder on both servers.

It appears to replicate ok, viewing the clients and policies, however it takes much longer than the other sites.

According to this document, it was suppose to bre resolved in this version:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/abcecc7098eced118825750d000f8cce?OpenDocument


In the release notes:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/2c62c4ee0e697aae882573b000034ded?OpenDocument

Symantec Endpoint Protection Manager replication fails with ASA error 193: "Primary Key for Table 'COMMAND' is not unique" when using an embedded database
Fix ID: 1533903
Symptom: Replication fails when the HARDWARE key is NULL.
Solution: Made changes to the query that finds the data.



I have two existing partners with my Main site which replicate without issue.

Hi Andrew,

Is it a fresh installation or an upgrade to MR4 MP2?

Regards,

This was an Upgrade to MR4 MP2

Hi Andrew, Did you deleted the replication partner before upgrading the manager to the latest version. Secondly the issue was there in MR4 MP1 as explained in the defect. If you have follow the upgrade process correctly and still you are getting the error. In that case I would request you create a case with support as soon as possible in order to get it problem diagnosed. Regards,

This site was standalone prior to the upgrade.
I upgraded to MR4 MP2 to match my Main Site's version in order to reconfigure it as an Additional Site for replication.

I will try removing the SEPM off this server, and doing a fresh MR4 MP2 installation.

Regards,
Andrew

Hi Andrew, You can try that and let us know the output for the same. Regards,

I completely removed SEPM off my Additional Site.
Reinstalled a fresh SEPM MR4 MP2 Additional Site.
The initial replication through the wizard completes successfully.
Log into SEPM fine. (Replication obviously worked)
Can see replicated clients and policies.

However, my scheduled replication errors as mentioned in my first post.
The Additional Site prepares about a 4mb data.zip file, this is received by the main site.
The Main Site, prepares and sends a similar sized data.zip file, which is received by the additional site. It is once it's decompressed the zip file (replication\inbox\) that it reports the error.

Please help, as I don't believe my site is replicating correctly. Let me know what errors/logs I need to submit.

Regards,
Andrew

Symantec Endpoint Protection Manager Log Collecting Tool
 

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091816421848

Thanks, I'll open a case.

You said you uninstalled & reinstalled the Addtional site right?

The main site is still having the old SEPM?

The Main Site is also running MR4 MP2, and is replicating fine with 2 existing Additional Sites. Only this third Additional Site is erroring during replication.