vCenter Server linked Mode. Error 28039. Setup cannot join vCenter Server to the linked mode group

[el_esceptico]

Hello,

I have the next error when I try to configure the server linked mode:

"Error 28039. Setup cannot join vCenter Server to the linked mode group. Refer to C:\documents and settings\...\...\jointool-0.log for more details"

I don't know what is the problem exactly. During this operation(configure vCenter server linked mode) the vCenter server and Webservices management services stop.

I have my both vCenter servers in a domain with DNS. The installation of vCenter I have done when the PCs were already inside the Domain.

Before of this error, appearing other error that it can't join to vcenter server and if I want to force this action. I force it and it appears the error that I have said before.

I don't know if this it is the correct comunity for putting this type of error.

Thank you in advanced.

[ealaqqad]

I have faced this problem once & posted the resolution at my blog. You can find the full resolution at:

vCenter Server linked Mode. Error 28039. Setup cannot join vCenter Server to the linked mode group

Please consider specially the part I had marked in Red. All the other parts are as important, but most people usually miss that part.

If this help you resolve this problem, which I am sure it would. Please be kind enough and give some points.

Best Regards,

Eiad Al-Aqqad

System X & Storage Technical Specialist

[el_esceptico]

Voy a permanecer fuera de la oficina desde el viernes 31 de Julio hasta el domingo 22 de Agosto. Para cualquier problema o tema urgente pueden ponerse en contacto con Francisco Cerezo(fcerezo@distrilogie.es) o con Clara Alvaro(calvaro@distrilogie.es) o en el teléfono 91 746 02 20.

Muchas gracias.

Un saludo.

Eduardo.

This e-mail and any attached files are confidential, intended solely for the use of the addressee, and may be legally privileged. If you are not the intended addressee, you are hereby notified that any disclosure, reproduction, copying, distribution or other dissemination or use of this e-mail is strictly prohibited. If you have mistakenly received this e-mail, please notify us immediately and then delete this e-mail from your system. This e-mail sent to and from our company is professional in nature and may be monitored to ensure compliance with internal policies and to protect our business. This e-mail does not constitute a commitment by Distrilogie, unless it contains an express statement to the contrary from an authorized representative. This e-mail and its transmission cannot be guaranteed to be secure or error free as they can be intercepted, corrupted, amended, lost or destroyed, arrive late, or contain viruses. Distrilogie or its affiliated entities are in no way liable for any errors or omissions in the content of this e-mail. Thank you.

[GalNeb]

I finally nailed down my 28039 error:

This is from my log:

Operation "Join instance VMwareVCMSDS" failed: : Action: Join Instance

Action: Join Instance

Action: Create replica instance

Action: Create Instance

Problem: Creation of instance VMwareVCMSDS failed: Active Directory could not create the NTDS Settings object for this directory server CN=NTDS Settings,CN=VCENTER67$VMwareVCMSDS,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={0E66679B-2F2D-4BCD-9B23-1E0CF75D6B63} on the remote directory server vCenter66.vi3.vm:389. Ensure the provided network credentials have sufficient permissions.

Error code: 0x800706ec

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

The key is the error on the last two lines. RPC is failing. Bottom line, turn off the firewall.

I finally found the answer. It has to do with the installation of ADAM and RPC. I found the following on another site:

"On investigation we found that ADAM requires 2 more addtional ports (Port 135 & a random port between 1025-65535) other than port 2000 to be opened at firewall. If I open those ports I replication happens without any Issues."

[Rockapot]

Nice.., the client i am working with now had the firewall turned off however the firewall was still binded to the local area connections. Once unbinded the errors went away and Linked Mode started functioning as expected.

Carl