Replication error: Metadata with Id B1A8A351B5CF09E95FEF09E9131CBFD4 could not be merged

Products

• Endpoint Protection

Issue/Introduction

Replication is failing after upgrade Symantec Endpoint Protection Manager (SEPM) to 14.3 RU3.

February 14, 2022 3:28:43 PM PST:  Replication from remote site BBBBD to local site AAAA finished unsuccessfully  [Site: AAAA]  [Server: SEPM]
February 14, 2022 3:28:42 PM PST:  Unexpected server error.  [Site: AAAA]  [Server: SEPM]
February 14, 2022 3:28:42 PM PST:  Unable to fetch changed data from remote site [BBBBD]: null  [Site: AAAA]  [Server: SEPM]
February 14, 2022 3:28:40 PM PST:  Unexpected server error.  [Site: AAAA]  [Server: SEPM]
February 14, 2022 3:28:39 PM PST:  Metadata with Id B1A8A351B5CF09E95FEF09E9131CBFD4 could not be merged  [Site: AAAA]  [Server: SEPM]
February 14, 2022 3:28:39 PM PST:  Unexpected server error.  [Site: AAAA]  [Server: SEPM] 

<SEPM install folder>\tomcat\logs\ReplicationLocal-x.log:

2022-01-27 13:26:46.682 THREAD 334 WARNING: ReplicationTask>> mergeMetadata: Error-> Merge Failed - Metadata with Id B1A8A351B5CF09E95FEF09E9131CBFD4 could not be merged
2022-01-27 13:26:46.682 THREAD 334 WARNING: java.lang.NullPointerException
 at com.sygate.scm.server.liveupdate.LuDownloadedContentArrayReplicationMerger.isSecurityFixSoftwarePackage(LuDownloadedContentArrayReplicationMerger.java:190)
 at com.sygate.scm.server.liveupdate.LuDownloadedContentArrayReplicationMerger.isMatchingChildLuPackageContent(LuDownloadedContentArrayReplicationMerger.java:164)
 at com.sygate.scm.server.liveupdate.LuDownloadedContentArrayReplicationMerger.getMatchingChild(LuDownloadedContentArrayReplicationMerger.java:136)
 at com.sygate.scm.server.util.merge.AbstractMerger.processChildren(AbstractMerger.java:444)
 at com.sygate.scm.server.liveupdate.LuDownloadedContentArrayReplicationMerger.merge(LuDownloadedContentArrayReplicationMerger.java:105)
 at com.sygate.scm.server.util.merge.AbstractMerger.doMerge(AbstractMerger.java:311) 
 ...

Environment

• SEPM 14.3 RU3

Resolution

This issue is fixed in Symantec Endpoint Protection 14.3 RU4 (14.3.7388.4000). For information on how to obtain the latest build of Symantec Endpoint Protection, see Download the latest version of Symantec software.