The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in %2 at any time. Files can be saved from deletion by copying them out of %2. Copying the files into %1 may lead to name conflicts if the files already exist on some other replicating partner. In some cases, the File Replication Service may copy a file from %2 into %1 instead of replicating the file from some other replicating partner. Space can be recovered at any time by deleting the files in %2.
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file ...
The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in ...
The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. ...
The file replication service on the domain controller cannot communicate with the file replication service on this computer. ...
The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...