VMWare Server 2.0 - Unknown (Invalid) VM's

[Update: Current preferred method would be to change your system locale, unless you know how to remove the encoding from the .vmdk file itself as well. The second method works to bring a system back up quickly, but you will notice the vmdk shows up as 'invalid' which only becomes an issue if and when you decide to use snapshots.]
Summary:
This probably occurs on small percentage of users' systems who change their system locale from English to another language, then back. To fix this:
  • Change your system locale to match that listed in the vmx/vmsd file of your VM.
OR
  • Remove the Unknown (Invalid) VM from Inventory.
  • Open the vmx and/or vmsd file(s) with notepad or other text editor and delete the line that contains ".encoding = "[systemlocale]""
  • Then re-add it to Inventory.


Error:
The selected virtual machine is not recognized on this system. The cause of this problem may be that the virtual machine's .vmx file is corrupted, or that the virtual machine version is newer than is recognized by the host. You can remove the virtual machine from the inventory if you believe that it is not recoverable.

Click the link below to remove the virtual machine from the inventory.

Etc...

Configuration:
VMWare Server 2.0 Build 122956

25 comments:

ofer said...

Thanks..

Johnson said...

hi,i've got the same issue. I can't find the line in the file. and the problem is ALL vm machine can't add into the inventory
pls advise.
my mail: veritasfx@hotmail.com

Johnson said...

Thanks it works.

Johnson said...

I've been in the same problem. Your solution resolved it.
thanks very much.

ByteSphere Support said...

Worked like a charm!

Anonymous said...

I've been in the same problem. Your solution resolved it.

Thanks you so much

Anonymous said...

Same here, great post. Thanks!!!

Anonymous said...

it worked, and saved our lives!! thanks
Vmware should actually solve this bug by the way, its quite tricky!

Anonymous said...

I had the same problem. Your solution did it! Thanks

Anonymous said...

By the way I just noticed now that you may also have to remove the encoding line contained in some vmdk files, otherwise you may end up like me 5 minutes ago that was getting this "Invalid hard disk" error in the VMware Server Home Page and without being able to take snapshots.

K. Chris Nakagaki (Zsoldier) said...

Yeah, I noticed that too. I forgot to update the post regarding that. Can you post what you did to remove that encoding line from the vmdk file itself? I found it was just easier to switch the host system back to the language that the vmdk's were originally created in.

happie said...

Thanks so much.
I've been thinking it was due to difference of vm versions.
Now I can use a lot of appliances.

Anonymous said...

thanks, IT WORKS!!

Anonymous said...

Great post! It works!
If you split your hard drive several files(2 GB each?). You will have to edit the hard drive's vmdk file and delete that exact same line. otherwise, you are good to go!

Anonymous said...

Thanks alot you saved our lives
Worked like a charm!

Mickey said...

Thank you very much..you just saved me hours of reinstalling the program!!..man..who might have thought that changing the system locale will screw up the virtual machine!

Anonymous said...

Many thanks! Great post!

liron said...

Thanks, that was the solution !!!
Good post!

Anonymous said...

Thanks. Tihs thread is a life saver. I had to delete some snapshot files and suspension files as well. Regards...

Anonymous said...

Tnx, it's works. :)

Behnoud said...

Thank You.

Pardeep said...

Hi, I can't find the line in the file and the problem is still presist, getting unknown (Invalid).

by the way: what is the soluations?

Please advice.

K. Chris Nakagaki (Zsoldier) said...

@Pardeep - Need more information about your setup to assist. I suggest posting to the vmware communities board as this may not be related. http://communities.vmware.com

Anonymous said...

super! worked for me also!

Kenneth Chung said...

Thank you very much. You saved my life :)