On a Windows Server 2003-based computer, the Virtual Disk Service and the Logical Disk Manager Administrative Service may stop responding after you unmount volumes that are created for transportable snapshots

Consider the following scenario. You import some transportable snapshots on a Windows Server 2003-based computer. Then, you unmount the volumes that are created for the snapshots. In this scenario, the Virtual Disk Service and the Logical Disk Manager Administrative Service may stop responding.

When this problem occurs, the volumes are not unmounted as expected. You see the drive letters of the volumes in Windows Explorer. However, a red "X" appears on each volume.

Additionally, the following events are logged in the System log:

Event ID 15

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 15
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The device, <Device name>, is not ready for access yet.

Event ID 1

Event Type: Error
Event Source: Virtual Disk Service
Event Category: None
Event ID: 1
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Unexpected failure. Error code: <Error code>

This problem occurs because a timing issue in the Logical Disk Manager Administrative Service causes a deadlock condition.

Service pack information

To resolve this problem, install the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 have Windows Server 2003 Service Pack 1 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003, x64-based versions

To work around this problem, manually stop the DMAdmin.exe process.

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: