Guys,
Need a little help I'm running the following
vCenter Server 4.0.0 (build 208111)
ESX Server 4.0.0 (build 208167)
I have a VM running WIndows 2000 Advanced and when I try and open the console I get a black screen and the followin error messsage
" Unable to connect to MKS: Virtual machine config file does not exist".
I've browsed the datastore and all the VM files appear to be in place, I was thinking of deletin the VM from the inventory and re-adding the vmdk file, would this be a good idea?
Thanks.
Removing and re-adding it to the inventory will not do any harm (you might loose historial data for the VM), but will not likely solve the problem.
I doubt this is a problem with the .vmx file, but you can try:
- Remove VM from inventory
- Create new VM (with the same specs as the VM you removed), name it differently and do not add any hard disks to it
- Edit the new VM settings and add the existing vmdks from the VM you removed
- Power on VM and try
you should still have your entire original VM folder intact, in case you need it, you'll always have your original vmx file to add it back to the inventory.
By doing the above steps you recreate the vmx file.
f this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!
Does this happen if you connect to the console via vCenter Server AND directly to the ESX server?
If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!
Yes same error both times.
Is it only this VM or more than one? Try a different one with the same OS.
Check in the settings of the VM - the path to the datastore that the VM thinks it's using.
This is sometimes weirdly a DNS issue too - ensure that your ESX servers have the same DNS settings, all hostnames in lowercase etc and can each resolve each other.
Other forum posts have suggested re-adding to the inventory, one post even resolved it by restarting the vpxa agent on the host.
dan
Try connecting to the ESX and vCenter server via IP address.
I've seen this error go away before by removing vSphere client, removing all folders and references from you workstation and installing again, but this should be the last resort before trying other approaches.
If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!
This is the only VM in the whold datacenter that is experiencing this issue. Storage path's seem fine (I can browse the datastore the VM resides on). Should I just try removing and re-adding it to vCenter, it shouldnt do any harm right?
Removing and re-adding it to the inventory will not do any harm (you might loose historial data for the VM), but will not likely solve the problem.
I doubt this is a problem with the .vmx file, but you can try:
- Remove VM from inventory
- Create new VM (with the same specs as the VM you removed), name it differently and do not add any hard disks to it
- Edit the new VM settings and add the existing vmdks from the VM you removed
- Power on VM and try
you should still have your entire original VM folder intact, in case you need it, you'll always have your original vmx file to add it back to the inventory.
By doing the above steps you recreate the vmx file.
f this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!
try adding the name and ip address of your host and vcenter server here:
C:\WINDOWS\system32\drivers\etc\hosts file
maybe even add the name and ip of the VM you are trying to connect to.
Virtual machine config file does not exist".
are you sure the file exists - and if it exists wether it is valid ?
Maybe the vmx is corrupt ?
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
Hi,
@piaroa:
I have the same problem with a VM on an ESXi 5.0 host. Does your solution works on that either ?