StoreVirtual Storage
1748181 Members
3322 Online
108759 Solutions
New Discussion

Problem installing VSA on ESXi 6.7 / vCenter 6.7

 
SOLVED
Go to solution
industriellIT
Occasional Collector

Problem installing VSA on ESXi 6.7 / vCenter 6.7

I need to install on my new ESXi 6.7 U1 hosts. 

Tried connecting the VSAinstaller to both vCenter and hosts, but get an error saying: 

"Installer could not connect to xxx

A connection failure occured (The underlaying connection was closed: An unexpected error occured on send.)"

 

Anyone know what might cause this error or any solution to it?

 

 

4 REPLIES 4
vlho
Advisor
Solution

Re: Problem installing VSA on ESXi 6.7 / vCenter 6.7

industriellIT
Occasional Collector

Re: Problem installing VSA on ESXi 6.7 / vCenter 6.7

I have tried to add these DWORDS (did not exist), and rebooted - problem still there when trying VSA installer.

Also tried installing .NET Framework 4.7.2, and rebooted - problem still there when trying VSA installer.

I do not use PowerCLI and does not have this on my computer.

 

Just as a curiosity I tried to connect to an older host with ESXi 6.0, this works.

industriellIT
Occasional Collector

Re: Problem installing VSA on ESXi 6.7 / vCenter 6.7

I did not notice that [NET.version] registry location.

So when I added the key to the right place and also started VSAinstaller from an administrator commandline windows it works! 

Thanks for the tip!

Registry added:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

SG25AK
Frequent Visitor

Re: Problem installing VSA on ESXi 6.7 / vCenter 6.7

Hi,

we have the same error when trying to install a FOM on 6.7 U2.

I have implemented the mentioned registry keys, restarted the system and started the installer from an admin command line - but to no avail. 

Is there any other solution to this? We already have a support ticket open, but the support engineer insist on that this error is environment specific.