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

Comments

John Li 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
February 2, 2009 at 5:11 AM
John Li said…
I've been in the same problem. Your solution resolved it.
thanks very much.
February 12, 2009 at 2:17 AM
Anonymous said…
Worked like a charm!
March 10, 2009 at 10:47 AM
Anonymous said…
I've been in the same problem. Your solution resolved it.

Thanks you so much
March 11, 2009 at 3:55 AM
Anonymous said…
Same here, great post. Thanks!!!
March 18, 2009 at 4:49 AM
Anonymous said…
it worked, and saved our lives!! thanks
Vmware should actually solve this bug by the way, its quite tricky!
June 20, 2009 at 10:00 AM
Anonymous said…
I had the same problem. Your solution did it! Thanks
June 24, 2009 at 7:00 AM
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.
June 24, 2009 at 7:32 AM
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.
June 25, 2009 at 9:04 AM
Unknown said…
Thanks so much.
I've been thinking it was due to difference of vm versions.
Now I can use a lot of appliances.
August 29, 2009 at 8:49 AM
Anonymous said…
thanks, IT WORKS!!
September 29, 2009 at 8:12 AM
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!
February 5, 2010 at 12:54 PM
Anonymous said…
Thanks alot you saved our lives
Worked like a charm!
February 15, 2010 at 4:45 AM
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!
February 21, 2010 at 7:46 AM
Anonymous said…
Many thanks! Great post!
March 4, 2010 at 1:44 PM
liron said…
Thanks, that was the solution !!!
Good post!
July 7, 2010 at 9:20 AM
Anonymous said…
Thanks. Tihs thread is a life saver. I had to delete some snapshot files and suspension files as well. Regards...
July 11, 2010 at 6:39 PM
Anonymous said…
Tnx, it's works. :)
July 21, 2010 at 12:51 AM
Unknown 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.
December 15, 2010 at 7:48 AM
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
December 15, 2010 at 12:58 PM
Anonymous said…
super! worked for me also!
January 8, 2012 at 3:03 PM
Kenneth Chung said…
Thank you very much. You saved my life :)
October 29, 2013 at 1:01 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more