This article describes an issue that occurs on Windows Server 2012 R2-based domain controllers. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

Consider the following scenario:

  • In an Active Directory environment, domain controllers are running Windows Server 2012 R2 with Identity Management for UNIX installed.

  • Password Synchronization is enabled on the domain controllers.

In this scenario, the domain controllers crash frequently.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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.

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, submit a request to 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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to 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 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17xxx

    Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 2012 R2

File name

File version

File size

Date

Time

Platform

Psadmin.exe

6.3.9600.17711

67,072

23-Feb-2015

02:09

x64

Pswdsync.dll

6.3.9600.17712

203,776

24-Feb-2015

00:43

x64

Psync-ppdlic.xrm-ms

Not applicable

2,875

24-Feb-2015

01:25

Not applicable

Psync.mof

Not applicable

2,361

18-Jun-2013

15:29

Not applicable

Psync_namespace.mof

Not applicable

122

18-Jun-2013

15:29

Not applicable

Psync_provreg.mof

Not applicable

499

18-Jun-2013

15:29

Not applicable

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File property

Value

File name

Amd64_c86eb242b5a9944aeb8144b51e720e36_31bf3856ad364e35_6.3.9600.17712_none_48d1d821890d3acc.manifest

File version

Not applicable

File size

716

Date (UTC)

24-Feb-2015

Time (UTC)

08:07

Platform

Not applicable

File name

Amd64_microsoft-windows-p..ord-synchronization_31bf3856ad364e35_6.3.9600.17712_none_567c85f3105af4a4.manifest

File version

Not applicable

File size

90,834

Date (UTC)

24-Feb-2015

Time (UTC)

02:12

Platform

Not applicable

Status

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

Cause

This issue occurs because an invalid socket handle is closed two times, and that causes the Lsass.exe process to crash.

References

See the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×