ERROR: Unable to connect to the MKS: the operation is not allowed in the current state.

[mrenf]

I am getting the error below when trying to connect to a windows XP VM i built running on one of our hosts.  I could connect to the VM after i built it and ran windows updates on it and then 2 weeks went by and i tried to connect to it and now i am getting this error.

I am able to connect to the VM using remote desktop but that is it.  I can restart the OS and uninstall and re install VM Tools.  But i am unable to connect to it from the vsphere client.  i was thinking of shutting down the VM from remote desktop but then if i do that i am unsure how to power it back up.  i checked and made sure i could ping from my vcenter server to the VM and back by FQDN and i can. Any tips or ideas how to resolve this?

[a_nut_in]

Hey Mrenf,

Try the following

1. vMotion the VM from one host to another and then check
2. If that does not work, try taking a vSphere Client session direct to the ESX host that has the VM and open the console from that host and check
3. If still does not work, just use RDP and log in to the VM and issue a reboot. Should come back fine post the reboot

Regards

a

[mrenf]

Cant vmotion cause i don't have HA configured on the cluster and if i reboot it it reboots fine but i can still only access using remote desktop.  So i tried to snapshot the VM and i get the following error "The attempted operation cannot be performed in the current state (Powered off)."

But as you can see in the screen shot Vsphere is showing the VM as being powered on and again i can remote desktop to it.

[a_nut_in]

Power down the VM, right click, remove from Inventory, browse datastore, right click on vmx file of the VM and add it back to the host, power it back on and check.

BTW is this VM running on snapshots? If so, commit snapshots first

[IQIT]

I had this same problem and vmotioning to another HOST to resolve the issue.

[AgentCK]

Same Problem with one of our VDP-Appliance. As you can see there are some nice alarms (all acknowledged) and it also affects our two servers for this cluster. The VDP ist accessible over the network via SSH, but there is still no response from the dpn (all commands are hanging). I guess, I've to delete the vdp and deploy a new one.

Sometimes I'm not happy with VMware ...

[ExpletiveDelete]

Every time this has happened to us, it was due to DNS and routing issues. We resolved by adding the vSphere host names (not the VM host names) to the local HOSTS file and that solved it. something simple to try.

[admin]

Can you try to close vSphere client connection and start a new session. I hope this will resolve the issue if not then uninstall vSphere client and reboot the system and again install vSphere client. Also if you will shutdown the VM it will power off the VM, you just need to power on the Vm from your client.

Thanks,

Dishank

[AgentCK]

@Dishank: Did you reply to me? In that case I have to tell you that you're too late. I've deleted the vdp appliance and redeployed a new one.

=> Problem solved.

[Anji2dudigam]

If you are getting at home lab please add your host (esxi) FQDN to your system host file available at c:Windows/system32/drivers/etc/host.

then you will definitely get result