The Virtual Server service may stop responding when the service is starting if one or more of the virtual machines are configured to automatically start when the Virtual Server service starts

On a computer that has Microsoft Virtual Server 2005 R2 Service Pack 1 (SP1) installed, the Virtual Server service may stop responding when the service is starting. This problem may occur if one or more of the virtual machines are configured to automatically start when the Virtual Server service starts.

To recover from this issue, you have to discard the saved state of the virtual machines. Or, you have to manually delete the corresponding saved state (.vsv) files of the virtual machines.

Additionally, you receive the following error message when you try to start a virtual machine:Additionally, the Internet Information Services (IIS) interface (Vswebapp.exe) and VMRC services no longer work, and you lose access to the Admin view.

A virtual machine may stop unexpectedly if the virtual machine is configured to automatically start when the Virtual Server service starts. Because the virtual machine stops unexpectedly, the virtual machine does not release all the resources. Then, the Virtual Server service stops responding.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Virtual Server 2005 R2 with Service Pack 1.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Virtual Server 2005 R2 with Service Pack 1, x86-based versions

Virtual Server 2005 R2 with Service Pack 1, x64-based versions

To work around this issue, use one of the following methods.

Method 1

Turn off the virtual machines, or shut down the guest operating systems, instead of saving the states.

Method 2

1. Create a virtual machine that has a blank virtual hard disk.
2. Connect the virtual machine to the same virtual network as the problematic virtual machines.
3. Turn on the virtual machine that you created in step 1.
4. Restore the problematic virtual machines.

Method 3

If the virtual machines do not have to have networking functionality, remove all the virtual network adapters that are connected to the virtual machines.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: