During an Active Directory replication request, the local domain controller (DC) identified a remote DC which has received ...

During an Active Directory replication request, the local domain controller (DC) identified  a remote DC which has received replication data from the local DC using already-acknowledged USN  tracking numbers.
  
  Because the remote DC believes it is has a more up-to-date Active Directory database than the  local DC, the remote DC will not apply future changes to its copy of the Active Directory  database or replicate them to its direct and transitive replication partners that originate from this  local DC.
  
  If not resolved immediately, this scenario will result in inconsistencies in the Active Directory databases  of this source DC and one or more direct and transitive replication partners. Specifically the  consistency of users, computers and trust relationships, their passwords, security groups,  security group memberships and other Active Directory configuration data may vary, affecting the ability to log on,  find objects of interest and perform other critical operations.
  
  To determine if this misconfiguration exists, query this event ID using http://support.microsoft.com  or contact your Microsoft product support.
  
  The most probable cause of this situation is the improper restore of Active Directory on the  local domain controller.
  
  The user has chosen to ignore this problem at their own peril.  
  User Actions:
  If this situation occurred because of an improper or unintended restore, forcibly demote the DC.  
  
Remote DC:
%1  
Partition:
%2  
USN reported by Remote DC:
%3  
USN reported by Local DC:
%4