The File Replication Service has detected what appears to be an attempt
to change the root path for the following replica set:
"%1"
This is not allowed. To perform this operation you must remove this member
from the replica set and add the member back with the new root path.
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 delete and re-add this member to the replica set.
Information related to this event is shown below:
Computer DNS name is "%2"
Replica set member name is "%3"
The current Replica set root path is "%4"
The desired new Replica set root path is "%5"
Replica staging directory path is "%6"
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 ...
The File Replication Service is deleting this computer from the replica set "%1" as an attempt to recover from the error ...
The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
The File Replication Service is no longer preventing the computer %1 from becoming a domain controller. The system volume ...