Tuple index is corrupted in a Windows Server 2008 domain or in an LDS instance

Symptoms

Assume that you define a tuple index for an Active Directory attribute in a Windows Server 2008 domain or in a Lightweight Directory Services (LDS) instance. The attribute has multiple values. In this situation, you experience one or more of the following symptoms:
  • Queries run slowly.
  • Failures occur in applications or services that rely on the tuple index.
  • The Active Directory database engine ESE reports tuple index corruption.
  • The following event is logged in the Directory Service log on one domain controller in the domain:
    Event Type: Error
    Event Source: NTDS ISAM
    Event Category: Database Corruption
    Event ID: 467
    Date: <date & time>
    User: N/A
    Computer: <computer name>
    Description: NTDS (<PID>) NTDSA: Index <name> of table datatable is corrupted (0|1).

Cause

This issue occurs because the Active Directory database engine manages the tuple index for the attribute incorrectly.

Resolution

To resolve this issue, install the following hotfix package on all domain controllers or LDS instances in the forest. After you install the following hotfix, recover the database from the corrupted indexes.

To recover the database for the corrupted indexes, use one of the following methods:
  • Perform an offline database defragmentation. After you perform an offline database defragmentation, all index data is removed from the database. The indexes are rebuilt automatically when you restart the domain controller or LDS instance.
    For more information about how to perform an offline database defragmentation, click the following article number to view the article in the Microsoft Knowledge Base:
    232122 Performing offline defragmentation of the Active Directory database
  • Remove and reinstall the affected domain controllers.

    Important Do not use the Install from Media (IFM) feature to perform this operation on a domain database, because the backup database may include the corrupted indexes.
  • If you know which attributes are affected, remove the index from these attributes, and then add the index back to them.

Hotfix information

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 the problem described in this article. 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 website: 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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, 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

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_f402ec88428bf2df.manifest
File versionNot applicable
File size8,529
Date (UTC)24-Nov-2012
Time (UTC)02:51
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_5021880bfae96415.manifest
File versionNot applicable
File size8,549
Date (UTC)24-Nov-2012
Time (UTC)03:52
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_f404907e4289fbdb.manifest
File versionNot applicable
File size8,539
Date (UTC)24-Nov-2012
Time (UTC)02:24
PlatformNot applicable
Properties

Article ID: 2786623 - Last Review: Jan 10, 2013 - Revision: 1

Windows Server 2008 Service Pack 2, Windows Server 2008 Datacenter, Windows Server 2008 Datacenter without Hyper-V, Windows Server 2008 Enterprise, Windows Server 2008 Enterprise without Hyper-V, Windows Server 2008 for Itanium-Based Systems, Windows Server 2008 Foundation, Windows Server 2008 Standard, Windows Server 2008 Standard without Hyper-V, Windows Web Server 2008

Feedback