<div>
Excellent. &nbsp;This leads to more questions, which I will raise separately. &nbsp;I think there are a number of wrongly-configured issues in my installation.
</div>


<div>
No problems, possibly, that's what we are here for....<br />
<br />
I hoped you used the Servers Vendors OEM ESXi version!<br />
<br />
e.g. downloaded from the Server Vendor, not VMware! and your server hardware is on the HCL!
</div>


<div>
I'm searching <a href="https://www.vmware.com/resources/compatibility/search.php" rel="ugc nofollow">https://www.vmware.com/resources/compatibility/search.php</a>&nbsp;...<br />
My server is an HP Pavilion Elite: &nbsp;&quot;HP-Pavilion BK237AA-ABL HPE-14f1f&quot; (on the host Configuration page)<br />
<br />
I haven't yet seen the VMware HCL ... and I can't determine if this machine is supported by searching this site.
</div>


<div>
Is that server ? Sounds like a desktop computer ?<br />
<br />
Is this for Office Production, or a Test and research lab ? to learn ESXi/vCenter Server ?<br />
<br />
It's not on the HCL!<br />
<br />
Check the <b>VMware Hardware Compatability Lists </b>HCL <a href="http://www.vmware.com/go/hcl" rel="ugc nofollow">here</a><br />
<br />
The VMware Hardware Compatibility List is the detailed lists showing actual vendor devices that are either physically tested or are similar to the devices tested by VMware or VMware partners. Items on the list are tested with VMware products and are known to operate correctly.Devices which are not on the list may function, but will not be supported by VMware. <br />
<br />
<a href="http://www.vmware.com/go/hcl" rel="ugc nofollow">http://www.vmware.com/go/hcl</a>
</div>


<div>
I'm guessing that Pavilion is a consumer desktop, and not included on any list of VMware supported hardware.<br />
<br />
It seems like Proliant is the HP model that is mostly supported by HP with regard to VMware.<br />
<br />
<a href="http://h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/vmware.aspx" rel="ugc nofollow">http://h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/vmware.aspx</a>
</div>


<div>
Yes, I am trying to prepare for VMware certification (maybe someday, a long time from now). &nbsp;This is my home office system.<br />
<br />
But it looks like I may be out of luck.<br />
<br />
I'm sure that the problem was triggered when I tried to access my datastore using the Web client. &nbsp;I wish there was an &quot;Undo&quot; for that step.
</div>


<div>
Correct, VMware HCL provides a list of qualified servers, which have been tested and supported with ESXi. Because it has a very small footprint. (e.g. less drivers for servers), it's also designed for Corporate Datacentres, and Business, which use Servers!<br />
<br />
But as this is for test, and you are not going to call VMware for Support, then your whitebox, which is what we call them, will suffice for testing for VMware Certs.<br />
<br />
Most of us, use whiteboxes for testing, and Dev, VMware training etc<br />
<br />
If you find any weird things happening that cannot be explained though, this could be the desktop!
</div>


<div>
P.S. &nbsp;A reboot fixed the &quot;Unable to connect to the MKS: Internal error&quot; problem.<br />
<br />
Thanks again.
</div>


<div>
What a junk answer you people are giving. It is ESXI installation issue. Mostly this issue is seen if you upgrade ESXI server and porting VM are &nbsp;not proper. <br />
<br />
Temp solution: restart the VM. [ power down and power up]. this will solve problem for temperory.
</div>


<div>
<div class="content wysiwyg-content">
My ESXi 6.0 installation was working fine until I installed vCenter Server.<br />
<br />
Unfortunately, I didn't have a procedure for installing vCenter Server, so I think I broke it when I added a new datastore.<br />
<br />
Now, from my vSphere Client, when I try to access my vm, I get the error &quot;Unable to connect to the MKS: Internal error&quot;<br />
<br />
Thanks for any help, hopefully the solution doesn't involve uninstalling vCenter Server.<br />
<br />
Obviously, I'm a novice at this.
</div>
</div>


My ESXi 6.0 installation was working fine until I installed vCenter Server.

Unfortunately, I didn't have a procedure for installing vCenter Server, so I think I broke it when I added a new datastore.

Now, from my vSphere Client, when I try to access my vm, I get the error "Unable to connect to the MKS: Internal error"

Thanks for any help, hopefully the solution doesn't involve uninstalling vCenter Server.

Obviously, I'm a novice at this.

ESXi error &quot;Unable to connect to the MKS: Internal error&quot;

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

ESXi error &quot;Unable to connect to the MKS: Internal error&quot;

ESXi error "Unable to connect to the MKS: Internal error"