Unable to connect MKS

1) MKS console fails to open with the error: the process /usr/lib/bin/vmware-vmkauthd-start failed to launch properly 
This issue occurs when the vmware-vmkauthd service cannot start due to insufficient memory. To resolve this issue, be sure to maintain adequate memory levels.
To ensure adequate available memory:
Check for resource pools having reservations over all available memory. If resource pools that exceed all available physical memory are detected, change the settings to ensure adequate space for system usage. For more information, see the Resource Management Guide for your version of ESX: 3.0 3.5 4.0 4.1
Restart the vmware-vmkauthd service using thiscommand:

#service vmware-vmkauthd restart
If the service was hung, it may still be running. In this case, run this command to kill the process:

#kill -9 <PID>

where <PID> is the PID of the service.
Run this command to start the service:

#service vmware-vmkauthd start
=================================
2) Unable to connect to the MKS: Error connecting to d:\Program Files (x86)\VMware\VMware server\x64\vmware-vmx.exe process.
If a virtual machine's console is blank VirtualCenter, restart the VirtualCenter Server.
-go into admin tools -&gt; services
-locate the VMWare Authorization service
-change the log on from Local System to a domain admin account.
-apply and ok. It will prompt you to restart the service to take affect, do this.
-if you try to log into the web interface and start a VM, you will get an access denied message
-go back into the VMware Authorization service, and change it back to Local System account, and restart the agent
====================================
3) Unable to connect to the MKS: Error
Kill any vmware-serverd processes with:
killall vmware-serverd
or
killall -9 vmware-serverd
Restart httpd with:
service httpd.vmware restart
The vmware-serverd processes should respawn automatically.
====================================
4) In the unlikely event that xinetd is not listening on port 902 for incoming ESX Server authd requests, you can restart xinetdusing:

service xinetd restart
====================================
5) VMware: VM Console error: Unable to connect to the MKS: Failed to connect to the server
To avoid losing access to the ESX host, perform the following steps:
Add the ESX server in your DNS
Edit your hostfile on the workstation (C:\Windows\System32\Drivers\etc\hosts\) and add your ESX server
===================================
6) VMware ESX Error: Unable to connect to the MKS: vmx connection handshake failed for mks of…
Edit the settings of the virtual machine, click the Options tab and make sure that the guest operating system version is correct. This can cause this error, so make sure you select the correct OS. E.g. “Microsoft Windows Server 2008 R2 (64-bit)”.
Try removing the virtual machine from the vCenter inventory and re-adding it.
Try restarting the VMware management agents (service mgmt-vmware restart and service vmware-vpxa restart).
===================================
7) When opening a virtual machine remote console you receive the error: Unknown MKS event
This issue occurs if TCP Port 903 is blocked. VMware Remote Console traffic flows directly over TCP port 903 between the workstation running the vCenter client and the ESX host.
Unblock TCP Port 903 in your firewall to resolve this issue. Refer to the firewall documentation or contact the firewall vendor's support for assistance in unblocking this port.
===================================  A virtual machine's console in VirtualCenter is blank and shows the message: Unknown MKS event
If a virtual machine's console is blank VirtualCenter, restart the VirtualCenter Server. For more information, see Stopping, starting, or restarting vCenter services (1003895).
===================================
9) Opening a console to a virtual machine fails with the error: Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached
Open a session to the vSphere Web Client.

https://vcenter_server_name:9443/vsphere-client
After connecting, right-click the affected virtual machine.
Click Configuration > Edit Settings....
Click VM options.
Click VMware Remote Console Options, then deselect Limit the number of simultaneous connections to this Virtual Machine.
Click OK.
Open a new console window to the virtual machine in the vSphere Client to verify.
Alternatively, add an entry to the configuration parameters of the virtual machine:
Power off the virtual machine.
Right-click the affected virtual machine and select Edit Settings....
Click the Options tab, then click General under Advanced.
Click Configuration Parameters....
Look for an entry named RemoteDisplay.maxConnections.
If the entry exists, set the Value to 1 or higher.
If the entry does not exist, click Add Row to add the parameter. The parameter details are:

Name: RemoteDisplay.maxConnections
Value: 10

Note: The Value can be set to 1 or more.
Power on the virtual machine.
Open a new console window to the virtual machine in the vSphere Client to verify.