A domain controller that is running Windows Server 2003 may restart unexpectedly if the Name Service Provider Interface API is used to query user account information that contains non-English characters

Consider the following scenario:

• A user account is created in a Windows Server 2003-based domain.
• Some attribute values of this user contain non-English characters.
• An application or a service queries this user account information by using the Name Service Provider Interface API.

In this scenario, you may receive the following error message on the domain controller, and the domain controller may automatically restart: Additionally, the following event is logged in the Application log:

Type: Error
Source: Winlogon
Event Category: None
Event ID: 1015
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code ErrorCode. The machine must now be restarted.

Consider the following as an example:

• Microsoft Exchange Server 2003 is installed on a domain controller that is running Windows Server 2003.
• A user account is created on the domain controller. Its Display Name and Alias attributes contain non-English characters.
  
  Note The Display Name field is located on the General tab and the Alias field is located on the Exchange General tab.
• An application, such as Microsoft Outlook queries for this user account information.

In this example, the Lsass.exe process that is running on the domain controller may cause the domain controller to restart.

This problem may occur because the Lsass.exe process calculates the buffer size for some attribute values of the user account incorrectly.

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 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

To apply this hotfix, the domain controller must be running Windows Server 2003 Service Pack 2 (SP2).

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

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.

For all supported x86-based versions of Windows Server 2003 SP2

For all supported Itanium-based versions of Windows Server 2003 SP2

For all supported x64-based versions of Windows Server 2003 SP2

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

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