Knowledge Base

Directory Service Does Not Start If Disk Is Full

Article ID: 259278

Article Last Modified on 2/28/2007

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server

This article was previously published under Q259278

SYMPTOMS

The following error message may occur when you start a Windows 2000-based Active Directory domain controller:

Lsass.exe - System Error

Directory Services could not start because of the following error: There is not enough space on the disk. Error Status: 0xc000007f. Please click OK to shutdown this system and reboot into Directory Service Restore Mode, check the event logs for more detailed information.

When this occurs, the following events are recorded in the Event log for the directory service:

Event ID: 1393
Attempts to update the Directory Service database are failing with error 112. Since Windows will be unable to log on users while this condition persists, the Netlogon service is being paused. Check to make sure that adequate free disk space is available on the drives where the directory database and log files reside.

Event ID: 428
NTDS (272) The database engine is rejecting update operations due to low free disk space on the log disk.

The following warning message is recorded in the System log:

Event ID 2013:
The D: disk is nearing Capacity. You may need to delete some files.

CAUSE

Active Directory cannot start if it runs out of disk space. Windows 2000 attempts to avoid this situation, but it can occur if you ignore warnings about low disk space in the System log or if you run large scripts against Active Directory for mass directory imports.

This behavior has been known to be caused by an issue with the NTBackup program not deleting old .edb log files. Please refer to this article for more information:

272425 Ntbackup.exe Does Not Truncate Active Directory Logs

RESOLUTION

To resolve this issue, use any of the following methods.

Method 1: Clear Space on the Drive

Use this method if you have one drive available and you cannot install additional drives in the server.

Click OK to acknowledge the error message so that the computer will reboot.
At the Boot menu, press F8.
Boot the domain controller into Directory Services Restore mode (Windows 2000 domain controllers only), and log on with the Directory Services Restore mode administrator account and password. (This is the password you assigned during the Dcpromo process).
Locate the drive containing the directory and log files. The directory (Ntds.dit) and log files are located in the \Winnt\Ntds folder on the root drive by default. However, the administrator may have changed their locations during the Dcpromo process.
Free some space on the drive. If there is no space to free, use method 2.
If you can free space on the drive, reboot the computer normally.

Method 2: Move the Database or Log Files

Ntdsutil.exe has an option for moving either the database file or the database log file. This method is ideal when you cannot move data to another drive to free more space. If all drives are at capacity, it may be necessary to install an additional hard disk in the computer.

Boot the domain controller in Directory Services Restore mode and log on with the Directory Services Restore mode administrator account and password (this is the password you assigned during the Dcpromo process).
At a command prompt, type ntdsutil.exe. You receive the following prompt:

ntdsutil:
Type files to receive the following prompt:

file maintenance:
Type info. Note the path of the database and log files.
To move the database, type move db to %s (where %s is the target folder).
To move the log files, type move logs to %s (where %s is the target folder).
Type quit twice to return to the command prompt.
Reboot the computer normally.

STATUS

This behavior is by design.

Additional query words: 0xc000000f temp.edb 268 439 specified

Keywords: kbenv kberrmsg kbprb KB259278

Microsoft KB Archive/259278

Contents