The remote server which is the owner of a FSMO role is not responding. This server has not replicated with the FSMO role ...

The remote server which is the owner of a FSMO role is not responding.  This server has not  replicated with the FSMO role owner recently.  
  
Operations which require contacting a FSMO operation master will fail until this condition is  corrected.  
  
FSMO Role: %1  
FSMO Server DN: %2  
Latency threshold (hours): %3  
Elapsed time since last successful replication (hours): %4  
  
User Action:  
  
This server has not replicated successfully with the FSMO role holder server.  
1. The FSMO role holder server may be down or not responding. Please address the problem with  this server.  
2. Determine whether the role is set properly on the FSMO role holder server. If the role needs to be adjusted, utilize NTDSUTIL.EXE to transfer or seize the role. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com.  
3. If the FSMO role holder server used to be a domain controller, but was not demoted successfully,  then the objects  representing that server are still in the forest. This can occur if a domain controller has its  operating system reinstalled or if a forced removal is performed.  These lingering state objects  should be removed using the NTDSUTIL.EXE metadata cleanup function.  
4. The FSMO role holder may not be a direct replication partner. If it is an indirect or  transitive partner, then there are one or more intermediate replication partners through which  replication data must flow. The total end to end replication latency should be smaller than the  replication latency threshold, or else this warning may be reported prematurely.  
5. Replication is blocked somewhere along the path of servers between the FSMO role holder  server and this server.  Consult your forest topology plan to determine the likely route for  replication between these servers. Check the status of replication using repadmin /showrepl at  each of these servers.  
  
The following operations may be impacted:  
Schema: You will no longer be able to modify the schema for this forest.  
Domain Naming: You will no longer be able to add or remove domains from this forest.  
PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory accounts.  
RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups.  
Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.