Dsamain.exe process crashes when AD LDS instance raises an exception in Windows 8.1 or Windows Server 2012 R2

This article describes an issue that occurs on a Windows 8.1 or Windows Server 2012 R2-based computer that has the Active Directory Lightweight Directory Services (AD LDS) server role installed. A hotfix is available to fix this issue. The hotfix has a prerequisite.

Symptoms

When this issue occurs, an event ID 1011 with the following information is raised in the Application Event log:

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this 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's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't 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 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't 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 doesn't 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 8.1 and 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's 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.16 xxx

    Windows 8.1 and Windows Server 2012 R2

    RTM

    GDR

    6.3.960 0.17xxx

    Windows 8.1 and 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 aren't listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Active directory diagnostics.xml

Not applicable

11,529

18-Jun-2013

12:21

Not applicable

Dsamain.exe

6.3.9600.17994

10,240

23-Jul-2015

16:53

x86

Ntdsbmsg.dll

6.3.9600.16384

2,048

22-Aug-2013

04:16

x86

Ntdsbsrv.dll

6.3.9600.17994

44,544

23-Jul-2015

16:43

x86

Ntdsctr.h

Not applicable

19,675

18-Jun-2013

12:21

Not applicable

Ntdsctrs.ini

Not applicable

55,536

18-Jun-2013

12:22

Not applicable

Ntdskcc.dll

6.3.9600.17994

134,656

23-Jul-2015

16:51

x86

Ntdsmsg.dll

6.3.9600.16384

4,608

22-Aug-2013

04:16

x86

Report.ad.xml

Not applicable

167,991

18-Jun-2013

12:21

Not applicable

Rules.ad.xml

Not applicable

33,911

18-Jun-2013

12:21

Not applicable

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Active directory diagnostics.xml

Not applicable

11,529

18-Jun-2013

14:46

Not applicable

Dsamain.exe

6.3.9600.17994

10,752

23-Jul-2015

17:42

x64

Ntdsbmsg.dll

6.3.9600.16384

2,048

22-Aug-2013

11:44

x64

Ntdsbsrv.dll

6.3.9600.17994

56,832

23-Jul-2015

17:30

x64

Ntdsctr.h

Not applicable

19,675

18-Jun-2013

14:45

Not applicable

Ntdsctrs.ini

Not applicable

55,536

18-Jun-2013

14:46

Not applicable

Ntdskcc.dll

6.3.9600.17994

194,048

23-Jul-2015

17:39

x64

Ntdsmsg.dll

6.3.9600.16384

4,608

22-Aug-2013

11:44

x64

Report.ad.xml

Not applicable

167,991

18-Jun-2013

14:46

Not applicable

Rules.ad.xml

Not applicable

33,911

18-Jun-2013

14:46

Not applicable

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1

File property

Value

File name

X86_bdb07ec6d5e584f235c2ba7ff323143f_31bf3856ad364e35_6.3.9600.17994_none_5e5108f03de1c102.manifest

File version

Not applicable

File size

716

Date (UTC)

24-Jul-2015

Time (UTC)

08:47

Platform

Not applicable

File name

X86_microsoft-windows-d..services-core-files_31bf3856ad364e35_6.3.9600.17994_none_24801be6429de1bb.manifest

File version

Not applicable

File size

11,809

Date (UTC)

24-Jul-2015

Time (UTC)

08:50

Platform

Not applicable

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

File property

Value

File name

Amd64_d3b2d66079595c62644acfa3ae9e1924_31bf3856ad364e35_6.3.9600.17994_none_774d29adf249aaf0.manifest

File version

Not applicable

File size

720

Date (UTC)

24-Jul-2015

Time (UTC)

08:47

Platform

Not applicable

File name

Amd64_microsoft-windows-d..services-core-files_31bf3856ad364e35_6.3.9600.17994_none_809eb769fafb52f1.manifest

File version

Not applicable

File size

11,813

Date (UTC)

24-Jul-2015

Time (UTC)

08:47

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

The issue occurs during a topology check by the knowledge consistency checker (KCC) to create the spanning tree algorithm.

During this process, Dsamain.exe references a NULL pointer, and the exception is raised.

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?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×