NDES stops working after you restart a Windows Server 2012 R2-based CA server

View products that this article applies to.

This article describes an issue that occurs after you restart a Windows Server 2012 R2-based certification authority (CA) server. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

When this issue occurs, you receive an error message that resembles the following on the Network Device Enrollment Service (NDES) server:

The Network Device Enrollment Service cannot submit the certificate request (0x80010108). The object invoked has disconnected from its clients.

In this situation, you have to restart the NDES server to clear the error message and then restore NDES connectivity to the CA server.

↑ Back to the top

Cause

This issue occurs because NDES maintains a DCOM connection to the CA server and uses this connection when NDES creates the certificate requests. If the CA server restarts, the connection becomes stale, and the requests made through NDES fail.

↑ Back to the top

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

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, 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 will have to restart the NDES server after this hotfix is applied to it.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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.

Version	Product	Milestone	Service branch
6.3.960 0.17xxx	Windows Server 2012 R2	RTM	GDR

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

File name	File version	File size	Date	Time	Platform
Mscep.dll	6.3.9600.17910	201,728	20-Jun-2015	18:58	x64

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_388c50f15cfce3b3c61404ca9d6cda99_31bf3856ad364e35_6.3.9600.17914_none_cc5de0bd189bc526.manifest
File version	Not applicable
File size	717
Date (UTC)	24-Jun-2015
Time (UTC)	23:54
Platform	Not applicable
File name	Amd64_microsoft-windows-c..icateservices-mscep_31bf3856ad364e35_6.3.9600.17914_none_55a00bf960ce55fc.manifest
File version	Not applicable
File size	38,679
Date (UTC)	24-Jun-2015
Time (UTC)	17:28
Platform	Not applicable