VCSA installation stuck at 80%

[vijayrana968]

Anyone faced this issue ? This was while when many of us were struggling with this including me but didn't find valid resolution.

ESXI host in licensed.

Tried with separate PSC and embedded as well.

DNS settings are in place.

[a_p_]

For how long did you wait so far? This step may take some time.

André

[vijayrana968]

It taking 5 hours to produce error.

[daphnissov]

It's probably an NTP issue or using wrong values during the installer wizard. Check previous post and if you can paste screenshots.

[vijayrana968]

I believe its NTP, I need to check for that. Values are correct as it won't allow to proceed if I put wrong values there. Thanks for the hint, I will check for NTP and revert back.

[daphnissov]

There are some values it will allow you to input and still proceed, for example the system name should not be an IP address (as some people seem to think) but a FQDN.

[vijayrana968]

So I pointed ESXI and installer workstation to same NTP source, how to point VCSA to this NTP when it is in installation state.

[daphnissov]

You'll have to redeploy.

[vijayrana968]

I found the issue is with esxi host AD integration, checking this.

[vijayrana968]

So its stuck at 80%, anyhow I managed to deploy it via tweak (installed on VMware Workstation and exported as OVA which I imported on ESXI). Now I can't find information how to install open-vm-tools on VMware photon. This would have installed by default if I installed it on ESXI host but I made a tweak so its not working.

[daphnissov]

Vijay, what is it you're doing here, exactly, and on what environment type? Can you please be explicit in describing your environment and circumstances? These types of installation issues only occur in a few circumstances, and it sounds like something is fundamentally wrong here. Unless you can fully describe your situation it's hard to know more to help.

[vijayrana968]

My Ravello lab washed up which had Windows based vCenter so building new vCenter as VCSA, no need to worry as its lab :smileyhappy: In Ravello I am trying to deploy VCSA as a Ravello VM (not VM on esxi host) since VCSA ISO won't work to boot on ravello so deploying it first on ESXI/Workstation so I can export from here and import as OVF at ravello. This is the way on ravello kb how to deploy VCSA as separate VM and not on ESXI.

[daphnissov]

Oook. So you are definitely doing something weird :smileyhappy:

Installation on Workstation shouldn't be much different, but you still need to ensure you have proper time keeping and using the proper values during installation and have forward and reverse DNS. Something else I've seen which causes hangups is when people try and drastically crank down on the VM's configuration. Leave the defaults at Tiny for the embedded model and see if it works. If it does, then you can try to reduce the vRAM if you must, but it usually won't work under about 8 GB.

If you've still having troubles deploying in Workstation, provide specifics (screenshots welcome) and let's see where it's falling down.

[MORENOHA]

Hi, I try mount my Lab in Ravello too, but I install ESX by .iso in VM ravello, and then, in other VM install and Windows Server 2012 inside in DNS server, and deploy VCSA, but this VCSA depend on ESX, and during installation asign IP ESX where VCSA will be work, but stuck at 80% in stage 1 installation later time out and fail it.

how are you doing? You at first mount VMworkstation inside Server Windows, deploy ESX and deploy VCSA inside this ESX, at the end, you export this VCSA VM and deploy in new VM ravello????

[Srinath Gunasekar]

In our case, the Temporary IP was which was used for new VCSA deployment was in different subnet than the actual Prod VCs' IP subnet. Hence, both the Source and the new VCSA were not communicating during the installation.
After providing the temporary IP address to the same subnet as the original VC the installation proceeded further.

[daphnissov]

Check NTP. You must have a valid internal NTP server for installation to succeed, and three sources must be pointed at the same NTP with their times sychronized: workstation where running installer; target ESXi host; and vCSA during installation process. Check all these points. If you're still getting a failure, please show screenshots of your installation process including all values in all stages.

[trailx]

Hi

I had exactly the same issue with this error message in log file (C:\Users\Administrator\AppData\Local\Temp\2\vcsaUiInstaller ):

 - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
 - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
 - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
 - debug: [1]pollRpmInstallProgress:getGuestFileErr:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.

To solve it, I launched the Management Console from VCSA (F2 Customize system) and reset VCSA appliance root password with the same one given during installation process.

[NRay]

Found a KB with the same log entries.

Please check the KB for more detail: failed to get filetransferinfo:serverfaultcode: failed to authenticate with the guest operating system using the supplied credentials

[makpaki]

quel est le mot de passe donner au départ ou comment réinitialisez le mot de passe

[vFantastic]

If it is NTP related try opening port 123 from the PC which deploys the VCSA and the NTP servers you set for the VCSA during installation.

[marcelo_soares]

It happened with me as well. It turns out to tbe the license on the ESX I was installing to (free one, it was for a lab). vCenter can´t be installed on a free ESXi - must be trial or licensed ESXi.

[jipharbers]

I've had this too. I wanted to redecorate my entire environment, so decided to reinstall vcenter. But every time installing it went wrong. So I also reset my ESXi servers. Again this problem, even after setting up NTP servers. As it turns out, the old Vcenter data remains in the data store. You can delete this (in ESXi's datastore, under data storage), and the installation should be successful afterwards. Good luck!

[AnasZak]

I know this is an old post. but the solution is simple.

Click on "Close" button, Connected to the VCSA on :5480 (remember the https) and continue on Stage 2 . Using ESXi Free.

[shakyak]

This worked for me. THanks

[zeemlinux]

Worked. Thanks

[Chirag235]

This worked for me. THanks

[ArmandoMiranda]

Me sucedio lo mismo con la version "VMware-VCSA-all-6.5.0-5973321.iso", tuve que descargar una version mas actual en donde solucionaron este problema, esta es la version que se instalo correctamente "VMware-VCSA-all-6.5.0-7070488.iso"

Saludos

[BBP]

  Yes I have also faced this issue many times. If the installation stuck at 80%, connect the vcsa appliance with port 5480 and proceed to stage 2.