Your domain controller restarts unexpectedly, and the Application log reports event ID 1015 and event ID 1000 in Windows Server 2003

Your Microsoft Windows Server 2003-based domain controller restarts unexpectedly. Additionally, the following events are logged in the Application event log:

Type: Error
Event ID: 1015
Source: Winlogon
Description: A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000354. The machine must now be restarted.

Type: Error
Event ID: 1000
Source: Application Error
Description: Faulting application lsass.exe, version 5.2.3790.0, faulting module ntdsa.dll, version 5.2.3790.0, fault address 0x0008590f.

This problem occurs if the following conditions are true:

• You recently used Lightweight Directory Access Protocol (LDAP) to modify or to add an Active Directory attribute value on a domain controller that is not a global catalog server. To modify or to add the attribute value, you used an account that has sufficient permissions.
• When you used LDAP, you supplied at least two distinguished name values. Additionally, the following conditions were true:
  • One or more of the distinguished name values had an incorrect syntax.
  • The other distinguished name value or values had the correct syntax and pointed to an existing object in a different domain.

In this scenario, an access violation occurs in the Lsass.exe process when the server performs a lookup of any distinguished name value that has an incorrect syntax.

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.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart your 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 tool in Control Panel.

Windows Server 2003, 32-bit editions

Windows Server 2003, 64-bit editions

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

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