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

Installing or Upgrading vCenter Server 6.0 with an external Platform Service Controller fails with the error: install.vmafd.join_vmdir_failed ERROR: 1, join vmdir failed (2117378)

  • 7 Ratings

Symptoms

  • Installing or upgrading vCenter Server 5.x to vCenter Server 6.0 using an external Platform Services Controller (PSC) fails with the error:

    install.vmafd.join_vmdir_failed
    ERROR: 1, join vmdir failed


  • In the C:\ProgramData\VMware\vCenterServer\logs\firstboot\vmafd-firstboot.py_ xxxx_stdout.log file, you see entries similar to:

    <YYYY-MM-DD>T<TIME>   Setting domain name  vsphere.local
    <YYYY-MM-DD>T<TIME>   Setting domain controller name PSC_FQDN
    <YYYY-MM-DD>T<TIME>   Setting PNID VCENTER_FQDN
    <YYYY-MM-DD>T<TIME>  Setting CA Path C:\ProgramData\VMware\vCenterServer\data\certs
    <YYYY-MM-DD>T<TIME>  Running command: [u'C:\\Program Files\\VMware\\vCenter Server\\vmafdd\\vmafd-cli', 'join-vmdir', '--server-name', 'PSC_FQDN
    ', '--user-name', 'Administrator', '--machine-name', 'VCENTER_FQDN', '--domain-name', 'vsphere.local']
    <YYYY-MM-DD>T<TIME>   VMAFD Boot failed


  • In the C:\ProgramData\VMware\vCenterServer\logs\firstboot\vmafd-firstboot.py_ xxxx_stderr.log file, You see entries similar to:

    C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\vmafdInstall.py:35: RuntimeWarning: to-Python converter for struct client already registered; second conversion method ignored. import vmafd
    <YYYY-MM-DD>T<TIME> AFD Join Domain Failed
    <YYYY-MM-DD>T<TIME> password: Error 19: Possible errors:
    LDAP error: Constraint violation
    Win Error: The media is write protected.
    <YYYY-MM-DD>T<TIME>   Exception: Traceback (most recent call last):
    File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 112, in main
    controller.client_mode()File "C:\Program Files\VMware\vCenter Server\firstboot\vmafd-firstboot.py", line 75, in client_mode service.client_mode()File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\vmafdInstall.py", line 684, in client_mode self.join_domain()
      File "C:\Program Files\VMware\vCenter Server\firstboot\identityinstall\vmafdInstall.py", line 381, in join_domain problemId = "install.vmafd.join_vmdir_failed")
    BaseInstallException: {
        "resolution": {
            "id": "install.vmafd.join_vmdir_failed.resolution",
            "localized": "Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request.",
            "translatable": "Please search of these symptoms in the VMware Knowledge Base for any known issues and possible workarounds. If none can be found, please collect a support bundle and open a support request."
        },
        "detail": [
            {
                "args": [
                    1
                ],
                "id": "install.vmafd.join_vmdir_failed",
                "localized": "ERROR: 1, join vmdir failed",
                "translatable": "ERROR: %(0)d, join vmdir failed"
            }
        ],
        "componentKey": "vmafd",
        "problemId": "install.vmafd.join_vmdir_failed"
    }

  • In the C:\ProgramData\VMware\vCenterServer\logs\vmdird\vmafdvmdirclient.log file, you see entries similar to:

    <YYYY-MM-DD>T<TIME>:t@9484512:ERROR: VmDirLdapSetupComputerAccount (cn=VCENTER_FQDN,ou=Computers,dc=vsphere,dc=local) failed with error (19)
    <YYYY-MM-DD>T<TIME>:t@9484512:ERROR: VmDirClientJoin failed. Error(19)


    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 


Cause

This issue occurs because of the stale data in the Platform Services Controller (PSC) due to old vCenter Single Sign-On installation data that existed at one time with the same fully qualified domain name as the failing vCenter Server 6.0 installation or upgrade. The vCenter Single Sign-On no longer exists but the references still exist in the running Platform Services Controller.

Resolution

To resolve this issue, clean the stale data from the Platform Service Controller.
 
To clean the stale data from the Platform Service Controller:
  1. Restore the failed vCenter Server 6.0 installation or upgrade to its previous state.  
  2. If you are upgrading from vCenter Server 5.x, stop the VMware VirtualCenter Server service and the VMwareVCMSDS services on the vCenter Server machine.
  3. Log in to the Platform Services Controller machine.
  4. Click Start > Run, type cmd, and press Enter.
  5. Navigate to the C:\Program Files\VMware\vCenter Server\vmdird location by running this command: 

    cd C:\Program Files\VMware\vCenter Server\vmdird

  6. Ensure that you provide the fully qualified domain name of the vCenter Server machine that is failing to install or upgrade by running this command:

    vdcleavefed.exe -h vcenter_fqdn -u Administrator

    Note: Enter the fully qualified domain name for vcenter_fqdn for vCenter Server that is currently failing to install or upgrade. This command prompts for the Administrator@vsphere.local password.

  7. Start the VMware VirtualCenter Server service and the VMwareVCMSDS services on the vCenter Server machine, if applicable. 
  8. Retry the installation or upgrade of vCenter Server 6.0 again.


See Also

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.

Feedback

  • 7 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.
  • 7 Ratings
Actions
KB: