Comments for V blog

Comment on Unable to connect to the MKS: Failed to connect to server XXXXXX:902 by Elvys

Elvys — Mon, 14 Nov 2011 18:16:21 +0000

I have the following error “Unable to connect to the KMS: Internal error” but it is not form ESX Server. All the setting in ESX Servers described above are already set. This error happen from Remote Console in vCloud Director.

Any thoughts.

Comment on Unable to connect to the MKS: Failed to connect to server XXXXXX:902 by Darto

Darto — Mon, 24 Oct 2011 03:13:15 +0000

Work like charm !!

1. firts try add hosts dns, then ping the host if reply then ..
2. seconds add vmauthd.server.alwaysProxy = “TRUE”

thanks for info

Comment on Unable to obtain hardware information for the selected machine by Patrick

Patrick — Thu, 15 Sep 2011 21:52:08 +0000

I found that if I did a reboot and clean shutdown of the VM to be cloned, the error vanished. I think it looks for the “clean shutdown” flag to be true before it will try and clone anything. Makes sense. Thanks for all the other tips, though, they were quite helpful!

Comment on Unable to obtain hardware information for the selected machine by Nick

Nick — Mon, 21 Mar 2011 16:56:17 +0000

If that doesn’t work, create a snapshot of the machine you are trying to copy then try the converter again. Strange, I know. But it worked for me

Comment on Unable to connect to the MKS: Failed to connect to server XXXXXX:902 by Ed Ward

Ed Ward — Mon, 31 Jan 2011 19:05:02 +0000

I’m having this same issue with ESXi 4.1. “vmauthd.server.alwaysProxy=TRUE” is already in there by default.

Comment on Unable to obtain hardware information for the selected machine by Sean

Sean — Tue, 21 Dec 2010 23:54:03 +0000

Fixed my issue immediately thanks!

Comment on Unable to obtain hardware information for the selected machine by Juarez

Juarez — Wed, 18 Aug 2010 19:01:54 +0000

I changed for Windows 2008 64-bit and worked as well.