The Lsass.exe process exits unexpectedly on a domain controller that is running Windows Server 2008 R2 after a password is synchronized in Identity Management for UNIX (IDMU)

Consider the following scenario:

• You install the Password Synchronization component of Identity Management for UNIX (IDMU) on a domain controller that is running Windows Server 2008 R2.
• A password for a user is synchronized between the domain controller and a computer that is running UNIX or Linux.

In this scenario, the Local Security Authority (Lsass.exe) process exits unexpectedly on the domain controller, and then the domain controller restarts. Additionally, the following event is logged on the domain controller:

Alert: USER32 Event
Source: <full computer name>
Path:
Last modified by: System
Last modified time: <time>
Alert description: The process wininit.exe has initiated the restart of computer on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.

Note The "full computer name" placeholder represents the fully qualified domain name (FQDN) of the domain controller.

This problem occurs because of a code defect in the Password Synchronization component. This code defect affects the memory size calculation for the heap allocation.

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, your computer must be running Windows Server 2008 R2. Additionally, the Password Synchronization component must be installed.

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

The English (United States) 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 R2 file information notes

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 R2" section. MUM 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 x64-based versions of Windows Server 2008 R2

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

Steps to reproduce the problem

1. You install the Password Synchronization component of Identity Management for UNIX (IDMU) on a Windows Server 2008 R2-based domain controller.
2. You install the Password Synchronization single sign-on daemon on a computer that is running UNIX or Linux.
3. You change the password of a user on the computer that is running UNIX or Linux.

When the password synchronization process occurs between the computers, you encounter the problem that is mentioned in the "Symptoms" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.