ESXi Commands Fail with "Cannot verify server host key" Exception (4219307)

When attempting to select a datastore for a newly registered ESXi host, an error similar to the following appears:

"An unexpected error was encountered while attempting to create a new library location. Surgient.Platform.Commands.CommandException: 00050011 Command 'Surgient.RemoteServerManager.make directory' did not complete successfully.... Result: Failed. Message: nsoftware.IPWorksSSH.IPWorksSSHSexecException: Cannot verify server host key."

A similar "cannot verify host key" error may appear when attempting other operations on an ESXi host.

The host key can become invalid, requiring it to be regenerated.

Connect to the ESXi host via ssh, delete the old dropbear key, and generate a new one using the commands below.

This resolution should only be attempted on a newly pooled host, before any other hosts have communicated with it. If other hosts have communicated with it, they will have its old key cached. If this is the case, a newly generated key won't match the cached one, causing other errors.

The ESXi host must have ssh access enabled. See VMware documentation for details on how to enable ssh.

Connect to the ESXi host via ssh and enter the following commands:

cd /etc/dropbear
rm dropbear_rsa_host_key
dropbearkey -t rsa -f dropbear_rsa_host_key