Common Replications issues in Active directory

Replication Error 1722 the RPC server is unavailable

1. Error 1722 the RPC server is unavailable.

->Dcdiag Ldap Binding Error 81.
->While trying to replicate the DCs then we are getting  1722 error -RPC service is unavailable.
->How to Troubleshoot :
->All the Above Error can come when other DC is not reachable on the network.
->1st we will ping the Dc,If DCs is down with any reason then we need to make it up.
-> If dc is pining then we can check cmd-> nslookup DC (if its not resolving then we need to verify          the DN setting ),Generally DNS causes the Replications issue.
->Check SRV records using command ->dcdiag  /s:dc2(server) /test:dns
->We can restart Netlogion service to register SRV Records
->At last we need to check Network latency by using cmd ->ping dc -i 1024(bytes), It wil help us to detect network latency and replication will not happen.

2. LDAP binding error :82
-> While running the command Repadmin /replsum and repadmin /bind DC1(dc name) ,we are getting LDAP Error 82 ,then we have to check event viewer of failed DC1(dc) -event Id- 4 will be generated with details-"Target service account password is different than what is configured on the kerberos key distribution center for that target service. (if this event id is generated then only we will follow the below steps)".

-> net stop kdc (stooping kdc services)
-> repadmin /replicate dc2 dc1 dc=domain,dc=com (dc2= should be source ,dc1=destination (failed one)
->-> We can also do it from site and services console and then connection object ->right click and replicate
-> net start kdc (starting kdc services)

=>Which event ID will check for replication issues.

 ->event viewer->applications and services logs ->Directory service and DFS replication (both the logs need to be checked before performing any troubleshooting). 


3. When We get Event ID- 1988 then its for lingering object 
->how to delete lingering object
->while running replication /replicate command we get error "insufficient attributes were given to create object " then we have to delete lingering object using below steps.
->1st we need to find the object GUID,which we can get it from event viewer -event Id-1988 and there we will get object GUID or we can use below command to find GUID of lingering object.

->Repadmin /showrepl DC1 > Showrepl.txt

->Object GUID will be as given below
DSA object GUID: 70ff33ce-2f41-4bf4-b7ca-7fa71d4ca13e

for removing lingering object

Repadmin /removelingeringobjects DC2 70ff33ce-2f41-4bf4-
b7ca-7fa71d4ca13e "dc=bish,dc=com"
/Advisory_mode