The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...

The File Replication Service has detected a duplicate connection object between
this computer "%7" and a computer named "%1".

This was detected for the following replica set:

    "%2"



This is not allowed and replication will not occur between these two
computers until the duplicate connection objects are removed.



It is possible that this is a transient error due to Active Directory
replication delays associated with updating FRS configuration objects.  If
file replication does not take place after an appropriate waiting time,
which could be several hours if cross site Active Directory replication
is required, you must manually delete the duplicate connection objects by
following the steps below:



 [1] Start the Active Directory Users and Computers Snapin.

 [2] Click the view button and advanced features to display the system node.

 [3] Click on "%3, %4, %5".

 [4] Under "%5" you will see one or more DFS related replica set objects.
Look for the FRS member object "%6" under the subtree for replica set "%2".

 [5] Under "%6" look for duplicate connections from "%1".

 [6] Delete all but one of the connections.

The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ... The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ... The File Replication Service failed a consistency check (%3) in "%1" at line %2. The File Replication Service will restart ... The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ... The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ... The File Replication Service has detected an enabled disk write cache on the drive containing the directory %2 on the computer ... The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional ... The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ... The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...