You receive a "-519 (JET_errLogSequenceEnd)" error message when you run Active Directory on a Windows 2000-based server (897682)

SYMPTOMS

When you run the Active Directory directory service on a Microsoft Windows 2000-based server, an Active Directory transaction log entry is not written as expected. You also receive the following error message:

-519 (JET_errLogSequenceEnd)

Additionally, the following error is logged in the Directory Service log:

Event : Error
Source : NTDS ISAM
Category: Logging/Recovery
ID: 413
User : N/A
Description : NTDS (248) Unable to create the log. The drive might be read-only, out of disk space, misconfigured, or corrupted. Error -519.

CAUSE

This issue occurs when the following conditions are true:

The transaction log has reached the maximum file-name increment of "Edbffff0.log."
The Edbffff0.log file has reached its maximum size limit.

When these conditions are true, Active Directory cannot create a new log file. Therefore, you receive the error message that is mentioned in the "Symptoms" section.

RESOLUTION

To resolve this issue, initialize the Active Directory transaction log. To do this, follow these steps:

On the Windows 2000-based server, start the Directory Service in recovery mode.
At the command prompt, type the following command lines. Press ENTER at the end of each line.
ntdsutil
files
header
recover
header
q
Semantic database analysis
go
q
To close the command prompt, type exit, and then press ENTER.
Click Start, click Run, type %systemroot%\ntds in the Open box, and then click OK.
In the Ntds folder, delete the following:
- The Edb.chk file
- All files that have the file name extension of .log
Restart Windows 2000.

MORE INFORMATION

By default, the transaction log for Active Directory is written to the %Systemroot%\Ntds\Edb.log file. When the Edb.log file reaches its maximum size limit, a new log file is created. This new log file is named Edb00001.log.

The Edb00001.log file logs transaction entries until this log file reaches its maximum size limit. Then, another new log file is created. This new log file is named Edb00002.log. A new log file is created every time that the previous log file reaches its maximum size limit. After the initial Edb.log file, the names of all subsequent files that are written to this transaction log are incremented along a range from Edb00001.log to Edbffff0.log.

For more information about Active Directory in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

247715 Circular logging for Active Directory

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

830408 Exchange database stores remain mounted although all transaction logs that are available to a storage group have been used

896001 An event is not logged in the Application log before the last available transaction log in the sequence is used in Exchange 2000 Server