Search the VMware Knowledge Base (KB)
View by Article ID

Forcing replication between ADAM databases (1021805)

  • 15 Ratings


  • Connection broker pool information between main and replica brokers is out of sync.
  • Newly created pool on one broker does not show on the Admin page of its replica broker.
  • Event logs on the Connection Brokers show that ADAM was unsuccessful in replicating with at least one other server for several hours.
  • The ADAM Windows Event viewer has entries similar to:

Error,"1864","05/12/2010 10:48:55","ADAM [VMwareVDMDS] Replication","5","NT AUTHORITY\ANONYMOUS LOGON","This is the replication status for the following directory partition on this directory server. Directory partition: CN=Configuration,CN={F8BD78C6-ACF1-47B6-96B5-2E4320461172} This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown, divided into the following intervals. More than 24 hours: 1 More than a week: 1 More than one month: 1 More than two months: 1 More than a tombstone lifetime: 0 Tombstone lifetime (days): 180 Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled. To identify the directory servers by name, use the dsdiag.exe tool. You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>"."


Run this command on all Connection Brokers in the same ADAM instance to show the replication neighbors and the last time they replicated (Note: In Windows 2008 R2, you must run the command in C:\WINDOWS\system32):

C:\WINDOWS\adam\repadmin.exe /showrepl localhost:389 DC=vdi,DC=vmware,DC=int

Run this command on all Connection Brokers in the same ADAM instance to force the replication:
C:\WINDOWS\adam\repadmin.exe /replicate localhost-FQDN:389 remote-host-FQDN:389 dc=vdi,dc=vmware,dc=int

Note: Replace localhost-FQDN to FQDN of local server and remotehost.-FQDN with FQDN of destination server. 

For example:

C:\WINDOWS\adam\repadmin.exe /replicate CS1.domain.local:389 CS2.domain.local:389 dc=vdi,dc=vmware,dc=int

Additional Information

Run this command to ensure that replication is not disabled:

repadmin /options localhost:389 -DISABLE_OUTBOUND_REPL -DISABLE_INBOUND_REPL


view-connection-server  view-adam-replication

See Also

Update History

09/18/2012 - Added Horizon View 5.0.x to Product Versions. 12/05/2013 - Added Horizon View 5.2.x and 5.3.x to Product Versions. 7/21/2014 - Added VMware View 6.0.x to Product Versions

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 15 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 15 Ratings