Troubleshooting corrupt VM configuration files with Virtual Server

Troubleshooting corrupt VM configuration files with Virtual Server

  • Comments 1

If you have an installation of Virtual Server that has been working correctly - but now you are finding that:

  1. The Administrative website loads, but does not display any virtual machines.
  2. The Administrative website loads, but displays an error message about a corrupt configuration file.
  3. The Administrative website fails to load and you get an error stating that the CGI application took too long to respond.

It is highly likely that you have a corrupt virtual machine configuration file (.VMC) that is causing this problem.  To figure out if this is the case you should:

  1. Open the Services manager under Windows and stop the "Virtual Server" service.
  2. Open "%allusersprofile%\Application Data\Microsoft\Virtual Server\Virtual Machines"
  3. Move all the .LNK files out of this directory into a temporary holding spot (I just use a new folder on my desktop).
  4. Use the Services manager to start the "Virtual Server" service.

If you can now load up the Virtual Server Administrative website with no problems - you do have a corrupt configuration (if the website still does not load - time to look elsewhere).  No you can go through the process of moving .LNK files back (and starting and stopping the "Virtual Server" service each time) until you narrow down the problematic configuration file.

Once you know which configuration file is causing the trouble - it is usually easiest to just delete it and create a new virtual machine that points to the virtual hard disks of the virtual machine in question.

Cheers,
Ben

Leave a Comment
  • Please add 4 and 4 and type the answer here:
  • Post
  • This might also be related to how Virtual Server checks to see if the virtual state file exists (by creating a directory of the same name.  If it can create the directory, it doesn't exist.  Unfortunately, it doesn't delete the directory, so when it goes to create the .vsv file of the same name, it obviously fails and virtual server goes slightly mental until you force it down, find the directories and delete them.  Then, for some bizarre reason, it doesn't recreate the folders and will properly recreate the .vsv files when it restarts)

    Just wish they would just check if the file exist the way most people do... ( http://blogs.msdn.com/oldnewthing/archive/2007/11/09/6001644.aspx )

Page 1 of 1 (1 items)