Error during installing VCSA6.7

[alhawary]

Hello guys,

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+

I found the solution. It's the ISO itself.

I calculated the MD5 and SHA for the ISO I'm using and found that it's different than the original one.

So I downloaded it again from VMware portal and it worked like charm.

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+

I really need your help with my problem ASAP, my VCSA 6.7 setup get stopped at 63% every time I try to install it.

1. The ESXi is installed on DELL PowerEdge R410
2. I'm using ESXi Ver: 6.7.0 Update 1 (Build 10302608), VCSA Ver: 6.7.0 (Build 10244745)
3. I tried to install from Windows Server 2016, Windows 8.1 x64 (2 different PCs), tried from a VM on the ESXi itself and remotely.
4. My ESXi still in an evaluation mode.
5. I'm sure that the forward and revers records are setup correctly, tried to ping and nslookup with full success.

I searched if there is any SW requirements for the deployment but I found nothing !

** I attached the log.

Last lines in the log:

2019-01-28T20:13:42.917Z - info: output:ERROR

+ <Errors>

+ <Error>

+ <Type>ovftool.http.send</Type>

+ <LocalizedMsg>

+ Failed to send http data

+ </LocalizedMsg>

+ </Error>

+ </Errors>

2019-01-28T20:13:46.843Z - info: output:RESULT

+ ERROR

2019-01-28T20:13:46.843Z - info: Xml output from ovftool: <data><ManifestValidate valid="true"/><Errors><Error><Type>ovftool.http.send</Type><LocalizedMsg>Failed to send http data</LocalizedMsg></Error></Errors></data>

2019-01-28T20:13:46.843Z - error: Ovf Service:vmrefFlag: false

2019-01-28T20:13:46.843Z - info: Cancelling timeout due to error from progress callback

2019-01-28T20:13:46.843Z - error: Progress Controller: [VCSA ERROR] - Progress callback error

2019-01-28T20:13:46.843Z - error: Progress Controller: [VCSA ERROR] - Details Failed to send http data

2019-01-28T20:13:46.863Z - info: Cancelling the ping timer for session mgmt

2019-01-28T20:13:46.863Z - info: Cancelling the ping timer for session mgmt

2019-01-28T20:13:46.965Z - info: ovfProcess child process exited with code 1

2019-01-28T20:14:18.297Z - info: Log file was saved at: C:\Users\Alhawary\Desktop\installer-20190128-215825772.log

[daphnissov]

Please show screenshots of your installation process that clearly show the values you're supplying during installation.

[vijayku]

This generally occurs due to issues with DNS, can you check if all the FQDN's and hostnames can be resolved with forward as well as reverse lookup. Also check that there are no multiple entries in DNS.

[HassanAlKak88]

Hello,

After checking your logs, I found the following:

Error: No VM found with hostname 192.168.1.104                                               2019-01-28T20:00:31

Error in getVmWithIPFQDN: No VM found with hostname 192.168.1.104          2019-01-28T20:00:31

So most probably, your issue related to DNS. Double check the IP 192.168.1.104 used has one DNS record and there is no conflict with other addresses.

And double check the name of this record is the same used during deployment.

Hereunder, the DNS requirement for VCSA:

DNS Requirements for the vCenter Server Appliance and Platform Services Controller Appliance

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

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[alhawary]

Thanks for your reply, the log itself showing the steps, however here it is:

And here it is the DNS confirmation:

And the result:

[alhawary]

Hello Mr Hassan, thanks for your efforts.

Here it is the records in my DNS for confirmation:

And the reverse zone:

You will find no duplication or any wrong !

[HassanAlKak88]

Hello again,

Do you have other VMs connected to this VM Network port group using the same sub-net 192.168.1.0 ?

I am asking because maybe there is some mis-configuration from network side.

Please clarify the uplinks configuration (Trunk/Access port), and from port group side (VM Network) there is some tagging or no ?

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

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[HassanAlKak88]

And maybe the below will be a workaround solution:

https://www.ivobeerens.nl/2018/09/12/vcenter-server-appliance-vcsa-failed-to-send-http-data-error/

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

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[alhawary]

Hello again and thanks for your reply.

This network is isolated as it's a test zone, so there is no machines physical/VMs but this ESXi and my PC ONLY.

For a while I did a reset for my ESXi so it using all default configuration.

It's a flat setup with no single parameter configured from my side except the hostname and the static IP for the ESXi itself.

[alhawary]

I already using my ESXi IP not hostname, could you please check my screenshots in previous reply ?

[HassanAlKak88]

Yeh, but how are you connected from your PC to ESXi server ? is there a switch in the middle ? And how can you reach the DNS server ?

And if you can create a test VM (Windows/Linus  ....etc), try to configure the network with an IP from same subnet and test the connectivity between and VM on ESXi box with the DNS server.

If a the Test VM can reach the DNS with the same network configuration and using th same port group "VM network". so your issue seems from DNS server, and please try the below:

• Go to DNS server, Clear the cache
• Waited  about 15 minutes, and apply the following: ipconfig /flushdns   and ipconfig /registerdns
• Re deploy VCSA

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

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[HassanAlKak88]

You are right,

Sorry I didn't notice that

[alhawary]

My all network connected through a SOHO unmanged switch [a hub] so there is no configuration to look into, I already used 3 different machines (one of them was a VM on the ESXi itself) with 3 different DNS products (MS, dmesq, SimpleDNS) one of them on the ESXi itself also (MS DNS)! I even used my DNS in production environment.

I created an MS VM on the ESXi with same IP and same name and it joined the domain perfectly (the domain and the DNS on the same ESXi so the internal and external connection is perfect).

Again, I don't know what's going on but it doesn't seem to be a DNS problem.

[HassanAlKak88]

can you ping your VCSA name directly without the domain name (not the fully FQDN)

per example: ping vcsa .  is it resolve the IP ?

[alhawary]

Using a joined PC, it resolves directly to vcsa.raya-eg.local and get the correct IP.

Using a non-joined PC, it doesn't resolve or ping !

But I think that's normal as the DNS needs a FQDN to operate with ! If I'm wrong, could you please show me how could I resolve that if I'm using "MS Win 2016 DNS Server" ?

[HassanAlKak88]

Can you try to upload the ISO package of vCenter to this test VM (join it to domain). and try to deploy the VCSA from there.

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

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[alhawary]

The screenshots up from this VM already :smileygrin:

[HassanAlKak88]

if possible, can i have a remote session to check this issue ?

[alhawary]

Oh! I'm really thankful to you. I'll send you the TeamViewer ID and Password in a private message in 2 minutes.

Thanks again

[HassanAlKak88]

Glad to be of service