VCSA 6.0 Failed to start services

[macqqqq]

hi everybody,

i have just installed to VCSA 6.0 on my  environment after first boot i got this error on home screen """failed to start servies. Firstboot Error."

and i can ping but i cant connect it via web browser, i thought some services dosent start but i am not sure how can i check it ?

which tool is more usefull ? Putty or PowerCLI ?

[bluebeamMT]

IntellaSight post is the best short term fix for this solution it seems.

5/4/2016 still broken and I have DNS entries.

Something like below - If I crossed it out that means its actually not an option as it will give you the error.
Confirmed - Deleted original deployment, started over and changed only what you see below, used IP instead of FQDN and used one DNS instead of two.

                  Best part is it gives a soft error for no FQDN warning you that you should really use a FQDN if you want to waste your time.

Also this - The nightmare of vCenter server appliance 6.0 installation | Curiosity killed the cat

[Giacom0]

Add something like the following to the hosts file.

192.168.28.69     vcsa.local

It would also be a good idea to add a DNS entry into your DNS server or router.

[ccbccherman]

I had to do the following for a successful upgrade.

1)  "The user associated with the DSN has insufficient privileges" when upgrading from vCenter Server 5....

2)  Change the information in the DSN to the IP address of the vCenter server

3) Add in the hosts file the FQDN and IP address of the vCenter server

Hope this helps others.

[Howiedog]

VmWare is becoming another behemoth like MS and going downhill just a fast

This error still happens 3 years later and the minions at vmware care NOT to fix it.

Who baked this crap into this installer where DNS is a must have. Come on dope heads. or the fact if you use IP as your FQDN, and want to change it, ohhh guess what, you have to re-deploy the whole bloody mess gain. What poor poor programming. Just changing the IP when first deployed was cluster fuc%.

Eg: I have vcenter5.1-windows based up and running for years. Upgrading to VCSA6, so I want to use another IP for deployment, make sure this mess works in the first place (although I deplore the web interface), then and oNLY then once I am happy that VCSA is playing nice, I want VCSA to use the old VCENTER IP I have been using for the last 5 frigging years. What a bunch donut shop butchers.

So sad that the bigger a company becomes, instead of getting better at what they do, it gets continually worse, more complicated/cryptic/convoluted and archaic.

My vmware frustrations this week.

just my 1c

[chiragbarot]

I too was facing same issue.

Solution: I setup DNS Server and created A Host record (ip address with hostname) of all VCSA I was going to install. Start fresh installation with correct DNS server ip address and it worked like a charm.
Hope this would resolve issue...