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 that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
The File Replication Service has detected that the staging path for the replica set %1 has changed. Current staging path ...
The File Replication Service has detected that the volume holding the FRS debug logs is running out of disk space. This will ...
The File Replication Service has detected that the volume hosting the path %1 is low on disk space. Files may not replicate ...
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 has skipped one or more files and/or directories during primary load of 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 ...