The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica root path is : "%2" Replica root volume is : "%3" A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons. [1] Volume "%3" has been formatted. [2] The NTFS USN journal on volume "%3" has been deleted. [3] The NTFS USN journal on volume "%3" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. [4] File Replication Service was not running on this computer for a long time. [5] File Replication Service could not keep up with the rate of Disk IO activity on "%3". Following recovery steps will be taken to automatically recover from this error state. [1] At the first poll which will occur in %4 minutes this computer will be deleted from the replica set. [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
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 one or more volumes on this computer have the same Volume Serial Number. File ...
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 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 ...