Extensible Storage Engine Database Becomes Corrupted During Consistency Check

This article was previously published under Q296981
This article has been archived. It is offered "as is" and will no longer be updated.
When an Extensible Storage Engine (ESENT) database is checking itself for consistency, database corruption may occur.
This issue can occur if a recovery fails during the redo phase of a ESENT database consistency check. The termination routine is not called with the proper error flag, and the database is marked as consistent even though recovery did not complete. The database can be attachable/mountable and then can become corrupted when it is used or if it is located on a drive that has low disk space.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 2.
ESENT databases are used with various components such as Dynamic Host Control Protocol (DHCP) and Windows Internet Name Service (WINS). Subsequent attempts to run recovery on the database do not succeed because the database is marked as being consistent. Because the corruption is logical, a database that is incorrectly marked as consistent can be successfully backed up and the backup does not detect any errors.

Article ID: 296981 - Last Review: 10/23/2013 18:53:51 - Revision: 3.2

  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Service Pack 1
  • kbnosurvey kbarchive kbbug kbfix kbprogramming KB296981