Drivers or hardware providers that use the Virtual Disk Service to manage hardware LUN IDs encounter exceptions after a disk is physically removed from a computer that is running Windows Server 2003

Article translations Article translations
Article ID: 960831 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

On a computer that is running Windows Server 2003, some drivers or hardware providers use the Virtual Disk Service (VDS) to manage hardware logical unit number (LUN) IDs. However, when a disk is physically removed from the computer, these drivers or hardware providers may encounter exceptions. Additional investigation indicates that an invalid hardware LUN ID is returned by the VDS. This behavior occurs if the corresponding hard disk has been removed.

This issue causes storage access exceptions. It also causes Hardware Compatibility Test (HCT) failure for some hardware providers.

This issue also occurs in Windows Server 2008. For more information about the same issue in Windows Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
960832 Drivers or hardware providers that use the Virtual Disk Service to manage hardware LUN IDs encounter exceptions after a disk is physically removed from a computer that is running Windows Server 2008

CAUSE

This issue occurs because the VDS does not remove hardware LUN ID as soon as the corresponding disk is removed.

RESOLUTION

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 the problem described in this article. 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:
http://support.microsoft.com/contactus/?ws=support
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, the computer must running Windows Server 2003 Service Pack 1 or Service Pack 2.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 SP1, x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Vds.exe5.2.3790.3316359,42430-Mar-200910:48x86SP1
Vdsbas.dll5.2.3790.3316147,96830-Mar-200913:01x86SP1
Vdsdyndr.dll5.2.3790.3316326,14430-Mar-200915:04x86SP1
Vdshba_i.mofNot Applicable13,96701-Jul-200709:45Not ApplicableSP1
Vdshba_u.mofNot Applicable34501-Jul-200709:45Not ApplicableSP1
Vdsldr.exe5.2.3790.274419,45611-Jul-200610:11x86SP1
Vdsutil.dll5.2.3790.331662,97630-Mar-200915:04x86SP1
Vds_ps.dll5.2.3790.274430,72012-Jul-200601:20x86SP1
Windows Server 2003 SP1, Itanium-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Vds.exe5.2.3790.33161,173,50430-Mar-200913:03IA-64SP1Not Applicable
Vdsbas.dll5.2.3790.3316503,80830-Mar-200913:03IA-64SP1Not Applicable
Vdsdyndr.dll5.2.3790.3316766,97630-Mar-200913:03IA-64SP1Not Applicable
Vdshba_i.mofNot Applicable13,96730-Mar-200913:03Not ApplicableSP1Not Applicable
Vdshba_u.mofNot Applicable34530-Mar-200913:03Not ApplicableSP1Not Applicable
Vdsldr.exe5.2.3790.274463,48830-Mar-200913:03IA-64SP1Not Applicable
Vdsutil.dll5.2.3790.3316175,10430-Mar-200913:03IA-64SP1Not Applicable
Vds_ps.dll5.2.3790.274445,56830-Mar-200913:03IA-64SP1Not Applicable
Wvds_ps.dll5.2.3790.274430,72030-Mar-200913:03x86SP1WOW
Windows Server 2003 and Windows XP, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Vds.exe5.2.3790.3316624,12830-Mar-200913:03x64SP1Not Applicable
Vdsbas.dll5.2.3790.3316263,68030-Mar-200913:03x64SP1Not Applicable
Vdsdyndr.dll5.2.3790.3316456,19230-Mar-200913:03x64SP1Not Applicable
Vdshba_i.mofNot Applicable13,96730-Mar-200913:03Not ApplicableSP1Not Applicable
Vdshba_u.mofNot Applicable34530-Mar-200913:03Not ApplicableSP1Not Applicable
Vdsldr.exe5.2.3790.274429,69630-Mar-200913:03x64SP1Not Applicable
Vdsutil.dll5.2.3790.331695,23230-Mar-200913:03x64SP1Not Applicable
Vds_ps.dll5.2.3790.274441,47230-Mar-200913:03x64SP1Not Applicable
Wvds_ps.dll5.2.3790.274430,72030-Mar-200913:03x86SP1WOW
Windows Server 2003 SP2, x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Vds.exe5.2.3790.4485359,42430-Mar-200911:04x86SP2
Vdsbas.dll5.2.3790.4485147,96830-Mar-200914:54x86SP2
Vdsdyndr.dll5.2.3790.4485326,65630-Mar-200914:54x86SP2
Vdsutil.dll5.2.3790.448562,97630-Mar-200914:54x86SP2
Windows Server 2003 SP2, Itanium-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Vds.exe5.2.3790.44851,173,50430-Mar-200913:08IA-64SP2
Vdsbas.dll5.2.3790.4485504,83230-Mar-200913:08IA-64SP2
Vdsdyndr.dll5.2.3790.4485768,51230-Mar-200913:08IA-64SP2
Vdsutil.dll5.2.3790.4485175,10430-Mar-200913:08IA-64SP2
Windows Server 2003 SP2 and Windows XP Service Pack 2 , x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirement
Vds.exe5.2.3790.4485624,12830-Mar-200913:12x64SP2
Vdsbas.dll5.2.3790.4485264,19230-Mar-200913:12x64SP2
Vdsdyndr.dll5.2.3790.4485456,70430-Mar-200913:12x64SP2
Vdsutil.dll5.2.3790.448595,23230-Mar-200913:12x64SP2

STATUS

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

MORE INFORMATION

If you check the VDS log file when this issue occurs, you find logged information that resembles the following:
(PID:4016,TID:3964,12:31:22) WARNING: Exception caught in AuxThread(service): C0000005
(PID:4016,TID:3964,12:31:22) LEAVE CVdsPnPNotificationManager::AuxThread()
For more information about how to enable VDS logging, click the following article number to view the article in the Microsoft Knowledge Base:
842011 How to turn on logging for the VDS in Windows Server 2003
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 960831 - Last Review: October 8, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows XP Professional x64 Edition
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB960831

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com