This article has been archived. It is offered "as is" and will no longer be updated.
You try to perform a system state backup on a domain controller that is running Microsoft Windows Server 2003 Service Pack 1 (SP1). However, the process that backs up the Active Directory database and the Active Directory log files fails. Additionally, an error message that resembles the following appears in the backup log:
Operation: Backup Active backup destination: File Media name: "sysstate.bkf created DD/DD/YYYY at HH:MM AM|PM"
Volume shadow copy creation: Attempt 1. "NTDS" has reported an error 0x800423f0. This is part of System State. The backup cannot continue.
Error returned while creating the volume shadow copy:800423f0. Aborting Backup.
This problem occurs if the Volume Shadow Copy Service (VSS) does not perform a volume snapshot of the drive that contains the log files. The VSS does not perform a volume snapshot if the following conditions are true:
Either the DIT volume or the volume that contains the Active Directory log files resides on the system drive.
The Active Directory log files have been moved from the system drive, and the DIT volume resides on the system drive.
The following table lists the outcome for five scenarios in which the DIT volume, the operating system, and the log files are stored on a computer. You cannot create system state backups for scenarios 3 and 4 on a computer that is running Windows Server 2003 SP1.
Note Letters C, D, and E represent drives on the domain controller. The drive letter assignments do not have to match the drive letter assignments in the table. The drive letters in the table indicate the relative placement of the operating system, the database, and the log files.
You may not experience this issue in the original release version of Windows Server 2003.
Service pack information
To 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 How to obtain the latest service pack for Windows Server 2003
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.
To install this hotfix, your computer must be running Windows Server 2003 Service Pack 1 (SP1).
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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, Itanium-based version
Windows Server 2003, x64-based version
Windows Server 2003, x86-based version
To work around this problem, use one of the following methods:
Store the DIT volume, the operating system, and the log files on the domain controller, as shown in scenarios 1, 2, or 5 in the "Cause" section.
Note Drive letter assignments on the domain controller do not have to match the letter assignments in the scenarios table.
You may have to relocate a DIT volume or the Active Directory log files from a domain controller that has been restarted in directory services repair mode.For more information about how to move the database and to move the log files, click the following article number to view the article in the Microsoft Knowledge Base:
816120 How to use Ntdsutil to manage Active Directory files from the command line in Windows Server 2003
If a domain controller configuration corresponds to scenarios 3 and 4, use the Ntbackup utility to select any file on the volume that includes Active Directory database files. This file can be a dummy file. In this configuration, this volume is backed up by the Ntbackup utility.
Microsoft 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.
You can install this hotfix at the same time that you install Windows Server 2003 SP1 on a domain controller. You can also install this hotfix on a domain controller that is already running Windows Server 2003 SP1. Or, you can install a slipstream version of Windows Server 2003 that includes this hotfix.For more information about the standard terminology that is used to describe Microsoft software updates, 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