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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.0.600
2.
22xxxWindows Server 2008
SP2
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Esent.dll |
6.0.6002.22985 |
1,460,736 |
24-Nov-2012 |
02:34 |
x86 |
For all supported x64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Esent.dll |
6.0.6002.22985 |
2,507,264 |
24-Nov-2012 |
03:34 |
x64 |
For all supported IA-64-based versions of Windows Server 2008
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Esent.dll |
6.0.6002.22985 |
3,594,240 |
24-Nov-2012 |
02:14 |
IA-64 |
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 name |
X86_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_f402ec88428bf2df.manifest |
|
File version |
Not applicable |
|
File size |
8,529 |
|
Date (UTC) |
24-Nov-2012 |
|
Time (UTC) |
02:51 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows Server 2008
|
File name |
Amd64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_5021880bfae96415.manifest |
|
File version |
Not applicable |
|
File size |
8,549 |
|
Date (UTC) |
24-Nov-2012 |
|
Time (UTC) |
03:52 |
|
Platform |
Not applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008
|
File name |
Ia64_microsoft-windows-e..estorageengine-isam_31bf3856ad364e35_6.0.6002.22985_none_f404907e4289fbdb.manifest |
|
File version |
Not applicable |
|
File size |
8,539 |
|
Date (UTC) |
24-Nov-2012 |
|
Time (UTC) |
02:24 |
|
Platform |
Not applicable |
