Unable to connect to the MKS: Error connecting to d:\Program
Posted: 05 Jun 2010, 15:49
Unable to connect to the MKS: Error connecting to d:\Program Files (x86)\VMware\VMware Server\x64\vmware-vmx.exe process
Original article: http://spininfo.homelinux.com/news/Virt ... xe_process.
All rights reserved to the author(s) of the original article.
I know this thread is slightly old, but I've been experiencing the same problem on several 2003 and 2008 servers recently. Here is what I've found has fixed it. VMware really should address some of the bugs with 2.0.1. Between this, and not being able to do much of anything in the Virtual Network editor as anyone besides a local admin is slightly annoying. (constructive critisism)
-go into admin tools -> 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
I'm not sure why this works, but it's worked for 5 different Windows servers for me. Something isn't kosher.
Original article: http://spininfo.homelinux.com/news/Virt ... xe_process.
All rights reserved to the author(s) of the original article.
I know this thread is slightly old, but I've been experiencing the same problem on several 2003 and 2008 servers recently. Here is what I've found has fixed it. VMware really should address some of the bugs with 2.0.1. Between this, and not being able to do much of anything in the Virtual Network editor as anyone besides a local admin is slightly annoying. (constructive critisism)
-go into admin tools -> 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
I'm not sure why this works, but it's worked for 5 different Windows servers for me. Something isn't kosher.