An �Event ID 467� database corruption error may be intermittently logged in the Directory Services event log on a Windows Server 2003-based domain controller

On a Microsoft Windows Server 2003-based domain controller, the following database corruption error may be intermittently logged in the Directory Services event log: Note Service Pack 1 is included in x64-based versions of Windows Server 2003.

The database engine cannot update certain indexes in Active Directory. This database problem occurs because of the problems with the code pages and language locales that are used in the Lsass.exe system process.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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 this specific problem. 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 Web site: 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.Important To resolve this problem in the Active Directory forest, you must apply the following hotfix on all domain controllers in the forest.

The next time that a domain controller restarts after you apply this hotfix, the affected indexes are deleted and rebuilt. Rebuilding the indexes adds time to the startup process, depending on the size of the local NTDS.dit database and on the server hardware.

Prerequisites

There are no prerequisites

Note Service Pack 1 is included in x64-based versions of Windows Server 2003.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, 32-bit versionsWindows Server 2003, 64-bit Itanium-based versionsWindows Server 2003, 64-bit x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

If the Event ID 467 error message cites a corrupted Unicode index, the following data is affected: If the Event ID 467 error message cites a corrupted ASCII index, the following data is affected: The occurrence of the corruption in the ASCII indexes depends on the following factors:

• The sequence of changes to attribute values in the index
• The changes to the C runtime locale in the LSASS.exe process that occur between the index changes

These dependencies are complex. Therefore, the occurrence of the problem is not deterministic.