“Invalid Virtual Machine Error” when opening VMWare machines on a VMServer hosted on 64 bit Windows x64

On our new server running Windows 2003 Server R2 x64 and VMWare Server V1.01 we always got the message “Invalid Virtual Machine Error” when we tried to open any virtual machine (created by another system) in the VMWare Console after copying it to the new server.

After googeling the issue this thread gave me the right idea:

If you’re using [VMWare Server Console] in local mode, switch to remote mode with a valid Admin-level login and try again.

I simply closed the Console, restarted it and entered my credentials instead of choosing “local mode”. Voilà, now it works!


13 Responses to ““Invalid Virtual Machine Error” when opening VMWare machines on a VMServer hosted on 64 bit Windows x64”

  1. Donna Lee Says:

    Thanks, I was having the exact same problem and in remote mode it is working great.

  2. Passer by Says:

    Thanks so much. You have just saved me hours of fustration.

  3. Dirk Says:

    Just a note: This also seems to happen with the 32bit version.

  4. Coop Says:

    I spent more than a few hours scouring VMWare’s forums and this solution was not mentioned but fixed my problem as well.

    THANK YOU !!!!!!!!!!!!

  5. pauli Says:

    I had the same problem with version 1.04. but not 1.03.
    Thanks for posting this.

  6. polarizer Says:

    This approach won’t work for me. I had exact the same issue, but using remote console was not the solution.

    I moved the directory with the vm in it to another place in file system and voila – it worked again. No idea why?! There were no file access permission problems.

    Ubuntu 7.10 after upgrade vmware to 1.04 and 1.05

    the polarizer

  7. alber_o Says:

    great, thx for your solution 🙂

  8. Rpage Says:

    THANK YOU VERY MUCH! I just moved 6 virtuals over to a new box & freaked out when I saw this error! It worked great in remote mode! (how strange!)

  9. bungle Says:

    ass = saved … thanks.

  10. sllub Says:

    THank you very much

  11. Trevor Pott Says:

    I agree with the above; ass=saved. You are a gentleman and a scholar, good sir.

  12. Mikkel Says:

    After having had this problem multiple times with different solutions (remote login instead of local, moving files to a new dir, deleting .lck files, rebooting server etc.) and just found a new one i would like to share:

    my vm’s are located on a network share that after being configured to be more secure couldn’t be “correctly accessed(?)” by the vmware service. Solution was to mount with this line instead (last two params did the trick this time – a year ago the file_mode and dir_mode did the trick but this wasn’t enough this time apparently, so they might be obsolete now…):

    root@server:/mnt# mount -t cifs // /mnt/nas/ -o rw,iocharset=utf8,file_mode=0777,dir_mode=0777,user=write,password=write,nosetuids,noperm

    Hope this helps someone out there 🙂

    • Mikkel Says:

      Christ. splitting the line so it can be seen in all its glory:

      root@server:/mnt# mount -t cifs // /mnt/nas/ -o rw,iocharset=utf8,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: