Vcenter 6.7 windows installation Failing.

[roopujwr]

Hi

I am running out the same error trying again and again while installing the vCenter 6.7 windows with embedded PSC controller. I am using windows 2016 server. I have installed the .net framework and cleanup up the registry entries. Almost every steps i have tried . But no luck. For reference i have attached the logs.

Its all in the Test environment.

I am expecting valuable support from anyone.

Thanks

[daphnissov]

Here's some valuable advice:  Don't install vCenter on Windows. Use the vCSA and problem is solved.

[diegodco31]

Hi

Check your configurations dns and ip:

ValidateFqdn: Asked to verify: "WinVcenter.roo.com"

2018-07-29 13:31:47.274-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: Failed to lookup "WinVcenter.roo.com" as an IPv4 address-only: 11001

2018-07-29 13:31:47.274-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: Failed to lookup "WinVcenter.roo.com" as an IPv6 address-only: 11001

2018-07-29 13:31:47.274-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: 1 of 1 IPv4 addresses are on the system (primary is okay)

2018-07-29 13:31:47.274-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: IPv4 is consistent and usable

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: GetFileVersion: File C:\Windows\system32\dnsapi.dll has file ver 6.3.14393.206

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: IsFQDN: FQDN check says 1 of 1 IPv4 addresses are on the system (primary is okay)

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: ValidateFqdn: 1 of 1 of FQDN IPs are on system

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: Primary IPv6 address is loopback

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: 1 of 1 IPv6 addresses are on the system (primary is okay)

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: CheckHostNameOrAddr: IPv6 is consistent and usable

2018-07-29 13:31:47.288-07:00| vcsInstUtil-8832884| I: Leaving function: VM_ValidateFqdn

Any reason to install vcenter for windows?

VMware has deprecated vCenter Server for Windows with the release of vSphere 6.7. Farewell, vCenter Server for Windows - VMware vSphere Blog

I recommend using the VCSA.

Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.

[roopujwr]

Hi Diego,

Thank you for the response. Yea i have missed that DNS configuration. Now i have lost my expectation and i have tried to deploy the vCenter 6.7 appliance this time. All DNS configurations are in good state. I was able to nslookup and ping using the IP address and Hostname from the target esxi Host and vcenter appliance shell console. Nowhere finding any issues,but still the deployment is not going through smoothly. I am able to complete the 1st step of deployment but after starting the configuration part its throwing error on 2 % on vmware authentication framework. Not able to find out the error from the logs. I have attached the tar file in original post. Please investigate and help me out to get the final resolution.

Thanks

[roopujwr]

Hey All,

After a little research on log files i have got the below error details from the logs.

Initializing Directory server instance ...

Vdcpromo failed. Error[9127]

Could not connect to VMware Directory Service via LDAP.

Verify VMware Directory Service is running on the appropriate system and is reachable from this host.

2018-08-12T17:23:09.461Z  <class 'cis.baseCISException.BaseInstallException'>

2018-08-12T17:23:09.462Z  Exception: Traceback (most recent call last):

  File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 177, in main

    controller.firstboot()

  File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 53, in firstboot

    self.init()

  File "/usr/lib/vmware-vmafd/firstboot/vmafd-firstboot.py", line 59, in init

    service.init()

  File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmdirInstall.py", line 404, in init

    self.setup_domain()

  File "/usr/lib/vmware-vmafd/firstboot/identityinstall/vmdirInstall.py", line 259, in setup_domain

    problemId = problem)

cis.baseCISException.BaseInstallException: {

    "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.",

        "id": "install.vmafd.vmdir_vdcpromo_error_23.resolution",

        "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."

    },

    "problemId": "install.vmafd.vmdir_vdcpromo_error_23",

    "componentKey": "vmafd",

    "detail": [

        {

            "localized": "Could not connect to VMware Directory Service via LDAP. Verify VMware Directory Service is running on the appropriate system and is reachable from this host.",

            "id": "install.vmafd.vmdir_vdcpromo_error_23",

            "translatable": "Could not connect to VMware Directory Service via LDAP. Verify VMware Directory Service is running on the appropriate system and is reachable from this host."

        }

Can anybody look into the above logs and help me to find out the work around for this error. I have tried the deployment lot of times but its not moving beyond 2% from the stage 2 process.

Thanks

[A13x]

Not too sure if anyone has told you but after stage 1 you can snapshot so before you attempt stage 2 you dont have to sit through the long wait of stage 1. Where are you running the installer from and have you checked the dns from there? is the time correctly setup and have you tried installing it to another esxi host.

I assume firewall is not blocking anything?

[roopujwr]

Hi

I am running this installation from my Domain controller which is hosted in different Esxi Host. And my DNS is configured in the same DC. My DC windows firewall is already disabled.

Regards

[jjdubs]

I know this doesn't apply to the original question but may help someone struggling with vCenter 6.7U3

Bug in vCenter posted here: VMware Knowledge Base