Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

VCenter start fails after demoting Domain Controller

$
0
0

Hi.

 

Instead of hijacking other one's thread having the same problem I decided to start a new thread, so sorry for double posting.

 

After promoting a new DC and demoting the old one we have the problem that VCenter 5.1a no longer starts.

 

Taking a look at the imsTrace.log file of SSOServer we see the following line:

 

Caused by: javax.resource.spi.ResourceAdapterInternalException: Unable to create managed connection olddc.ourdomain.com:3268

 

As we can see SSO still tries to contact the old dc now beeing a simple member server instead of the new one - the question is why?

 

We checked health of AD by running DCDIAG and BPA both not seeing any problems. Additionally we checked DNS by hand to ensure that no SRV or any other records are present which reference the old DC. Also all other AD dependent services like Exchange, SharePoint, DFS run without issue and do not indicate any problems.

 

We also found the krb5.conf file of SSO which still references the old DC by the following entry:

 

[realms]
OURDOMAIN.COM = {
    kdc = olddc.ourdomain.com
    default_domain = OURDOMAIN.COM
}

 

However changing that entry does not solve the problem because after a short period this entry is replaced automagically by ??? - that's the question.

 

Mybe someon else has some ideas what to check next.

 

Cheers.


Viewing all articles
Browse latest Browse all 179681

Trending Articles



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