Quantcast
Channel: VMware Communities : All Content - VMware vCenter™
Viewing all articles
Browse latest Browse all 24426

Replication errors after Migrating vCenter server to Windows 2012 R2 - which was in linked mode

$
0
0

Since migrating our test environment to a new 2012 R2 server, we have been getting the below replication errors for ADAM (VMwareVCMSDS) in the event logs of the server:

 

The attempt to establish a replication link for the following writable directory partition failed.

 

Directory partition:

CN=Schema,CN=Configuration,CN={C7040EF2-F6C7-4C6F-8977-86A6C4D6438B}

Source directory service:

CN=NTDS Settings,CN=VCENTER$VMwareVCMSDS\0ACNF:c2141938-26d3-436d-b545-0281a9d3df86,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={C7040EF2-F6C7-4C6F-8977-86A6C4D6438B}

Source directory service address:

VCENTER.domain.local:cda12eef-897b-4034-b603-b0a4a631f16b

Intersite transport (if any):

 

 

This directory service will be unable to replicate with the source directory service until this problem is corrected.

 

User Action

Verify if the source directory service is accessible or network connectivity is available.

 

Additional Data

Error value:

1772 The list of RPC servers available for the binding of auto handles has been exhausted.

 

I did some research and found this -http://enterpriseadmins.org/blog/virtualization/linked-mode-server-replacement-and-vmwarevcmsds-errors/

 

I followed this through but got right to the end and got the errors below

 

Errors23.jpg

 

If i look at active directory explorer on the vCenter server machine, I can see two test servers (Same name but different creation date, one is obviously the old one),does anyone know how I can follow the above through without any errors? or resolve this?

 

errors2.jpg


Viewing all articles
Browse latest Browse all 24426

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>