Article ID: 912063 - Last Review: October 11, 2007 - Revision: 2.7 A Windows Server 2003-based computer stops responding when you perform a backup of an Exchange Server database
On This PageSYMPTOMS
Consider the following scenario. On a Microsoft Windows Server 2003-based computer, you perform a backup of a Microsoft Exchange Server database. You perform this backup by using the Virtual Disk Service (VDS) QueryProviders method together with the Volume Shadow Copy Service. In this scenario, the Windows Server 2003-based computer stops responding (hangs).
Additionally, the following Error events are recorded in the System log:
Event Type: Error Event Source: DCOM Event Category: None Event ID: 10010 Date: Date Time: Time User: NT AUTHORITY\SYSTEM Computer: Computer_Name Description: The server {4FB6BB00-3347-11D0-B40A-00AA005FF586} did not register with DCOM within the required timeout.
Event Type: Error Event Source: VDS Dynamic Provider 1.0 Event Category: None Event ID: 1 Date: Date Time: Time User: User_Name Computer: Computer_Name Description: The provider failed to load. Error(8004241B).
Event Type: Error Event Source: Virtual Disk Service Event Category: None Event ID: 17 Date: Date Time: Time User: User_Name Computer: Computer_Name Description: VDS fails to launch provider {F96544E6-5C8D-47B9-AA6E-FD19AB278629}. Error code: 8004241B@02000012 CAUSEThis problem occurs because the backup operation does not release the Hidden and ReadOnly attributes of the snapshot volume as expected. Therefore, the snapshot process is performed repeatedly until the computer stops responding. RESOLUTIONService pack informationTo resolve this problem, obtain 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:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix informationA 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: http://support.microsoft.com/contactus/?ws=support
(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.PrerequisitesYou must be running Windows Server 2003 SP1 to install this hotfix.Note x64-based versions of Windows Server 2003 do not require this service pack. Restart requirementYou may have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 tool in Control Panel.Windows Server 2003, x86-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Technical support for Windows x64 editionsYour hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: http://www.microsoft.com/windowsxp/64bit/default.mspx
(http://www.microsoft.com/windowsxp/64bit/default.mspx)
For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site:http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx
(http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx)
APPLIES TO
| Article Translations
|
Back to the top
