I have deployed several ESXi hosts with VMware_ESXi_6.7.0_10302608_Custom_Cisco_22.214.171.124.iso + patched with ESXi670-201811001.zip. While deploying vCenter Appliance 6.7U1 (VMware-VCSA-all-6.7.0-10244745_6.7U1.ios) - Windows UI installer - I am getting the following error:
I tried it twice, same issue. Installer is stuck at 99% for hours.
The logs tell nothing of interest for the time mentioned.
Thanks for your help.
Deploying VMware-VCSA-all-6.7.0-8217866.iso works fine. All with the same parameters/values as used in VMware-VCSA-all-6.7.0-10244745. OK fine, I can patch this now to U1. However, I think this is not the idea in the first place. Anybody facing the same issue when deploying VMware-VCSA-all-6.7.0-10244745.iso (vCSA 6.7U1).
Thanks for your answer. Input values do not matter because it works in 6.7 and not in 6.7U1. Values are _identical_. Hence, it is independent of the given values, IP, mask, domain etc.
Input values do not matter because it works in 6.7 and not in 6.7U1. Values are _identical_. Hence, it is independent of the given values, IP, mask, domain etc.
Possibly, but that's an assumption. Would you supply them anyway or no?
I'm having this issue with VMware-VCSA-all-6.7.0-10244745 where it fails at 99%. I have tried the latest download VMware-VCSA-all-6.7.0-11726888 and it stops at 97%. The vCSA console was just a black screen with flashing cursor. Shut down and started up seems to start OK now but have the error shown below it's IP address "Vpxd VA Post-install script failed".
I have gone to a browser using the https://<FQDN>:5480 which shows :
I have tried accessing vCSA via SSH to check the logs but it doesn't understand standard linux commands?
There's a load of entries in the installer log saying failed to initiate file transfer due to current state. Then it carries on then there are a load of authentication failures but this is after it has created the VM. How are the credentials failing? I have given it the ESXi credentials and it has created the machine so can't be that and the vm gets created by the wizard so why would there be credential issues? I've attached the installer log from this morning test.
Check the time on your target ESXi host and the workstation from where you're running the wizard. They need to have their times in sync. I also noticed you have two DNS servers there. Are these both internal DNS which have both sets of records?
Failed with lowercase, trying uppercase. Noticed the host had a different secondary DNS to the installer so that has been changed to match. All DNS servers have the correct forward and reverse entries. The 172 and 192 DNS always had the correct entries but the 10 DNS that was secondary on the host didn't. I've rebooted the host and rechecked everything to make sure settings are applied. Time is synchronised on host and server that installer runs from. Running again now but it's late over here so I'll check in the morning. I'll let you know the outcome. Thanks
So to summarize:
If these two bullets above are true statements, check that your vCSA ISO download is not incomplete by comparing the hash to the one posted on the my.vmware.com portal. A corrupt download somewhere is know to cause failures.
NTP local machine running installer
They are synchronising the same time (hard to refresh and grab at same time:
Where do I set NTP on the vCSA before it fails?
I have changed the NTP on the local machine and the host to sbs2011.torgersens.local and verified the source is updating from the Windows machine. I have also changed the primary DNS to the secondary and vice versa in the vCSA server although they both have the same records. I'm running the install again with those changes applied.