"Unable to connect to the Mks:virtual machine config file does not exist."

Fault logging:

1, Environment: 

ESXi 5.1, VCenter 5.1;

2, fault Description:

A. When you open the VM console in Vcenter, the following error message is displayed:

"Unable to connect to the Mks:virtual machine config file does not exist."

b, the data store where these VMs are viewed is grayed out and the parentheses state is inactive.

C. This problem occurs as long as the VMS on this state data store are present.

3, fault resolution:

Navigate to "Memory" and click "Rescan All".

4, fault analysis:

From the console error, the hint that the virtual machine configuration file does not exist, it will be associated with the state of access to its storage, the results show a storage state exception, after the attempt to re-scan the status of normal, the VM console is back to normal. It can be judged as a storage anomaly, which may be a flash, or other problem.

5. Additional Information:

When you search for this error message, some articles prompt to restart the ESXi management agent can be resolved, refer to the following link:

http://www.virtualization.net/1513-unable-to-connect-to-mks-virtual-machine-config-file-does-not-exist/

http://ksitigarbha.blog.51cto.com/1013724/1395655

VMware KB articles can be found here:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displaykc&doctype=kc&externalid=2075206& sliceid=1&doctypeid=dt_kb_1_1&dialogid=768552424&stateid=1%200%20767386952

Http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId =2095390

This article is from the "vm-ecological" blog, make sure to keep this source http://2755788.blog.51cto.com/2745788/1730303

"Unable to connect to the Mks:virtual machine config file does not exist."