The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. Verify that the computer %2 is up and running. Verify that the File Replication Service is running on %2 by typing "net start ntfrs" on %2. Verify that the network is functioning between %1 and %2 by typing "ping %1" on %2 and "ping %2" on %1. If the pings succeed then retry the failed operation. If the pings fail then there may be problems with the DNS server. The DNS server is responsible for mapping computer names to IP addresses. The commands "ipconfig" and "nslookup" help diagnose problems with the DNS server. Typing "ipconfig /all" will list the computer's IP address and the IP address of the computer's DNS servers. Type "ping" to verify that a DNS server is available. The DNS mapping for %2 or %1 can be verified by typing "nslookup" and then typing "%2" and then "%1" on %1 and %2. Be sure to check out the DNS server on both %1 and %2; a DNS problem on either computer will prevent proper communication. Some network problems between %1 and %2 can be cleared up by flushing the DNS Resolver Cache. Type "ipconfig /flushdns". Some network problems between %1 and %2 can be cleared up by renewing the IP address. Type "ipconfig /release" followed by "ipconfig /renew". Some network problems between %1 and %2 can be cleared up by resetting the computer's DNS entry. Type "net stop NetLogon" followed by "net start NetLogon". Some problems between %1 and %2 can be cleared up by restarting the File Replication Service. Type "net stop ntfrs" followed by "net start ntfrs". Some problems between %1 and %2 can be cleared up by restarting the computers %1 and %2 AFTER CLOSING RUNNING APPLIATIONS, especially dcpromo. Click on Start, Shutdown, select Restart, and click on OK. Other network and computer problems are beyond the scope of this event log message.
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 ...
The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available ...
The File Replication Service successfully added the connections shown below to the replica set: "%1" %2 %3 %4 %5 %6 %7 %8 ...