You receive an "Error 0x8007042b" error message when you add or join a node to a cluster if you use NTLM version 2 in Windows Server 2003


Symptoms


When you try to add or to join a node to an existing cluster on a Windows Server 2003-based computer, you may receive the following error message:
Error 0x8007042b: The process terminated unexpectedly.
Also, entries that are similar to the following may be logged in the ClCfgSrv.log file:
[INFO] [BC] Cluster Service Win32 Exit Code= 0x00042b [INFO] [BC] Cluster Service Specific Exit Code= 0x001702 
Additionally, events that are similar to the following may be logged in the system event log on the joining node:

Event message 1Event message 2

Cause


This problem may occur when all of the following conditions are true:
  • You set the Network security: LAN Manager authentication level policy to Send NTLMv2 response only\refuse LM & NTLM.
  • You set the Network security: Minimum session security for NTLM SSP based (including secure RPC) clients policy to Require NTLMv2 session security.
  • You set the Network security: Minimum session security for NTLM SSP based (including secure RPC) servers policy to Require NTLMv2 session security.
This problem may also occur if you apply a high-security domain policy template because the following policy settings may be enabled by the high-security domain policy template:
  • Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
  • Network security: Minimum session security for NTLM SSP based (including secure RPC) servers
For more information about high-security domain policy templates, click the following article number to view the article in the Microsoft Knowledge Base:

816585 How to apply predefined security templates in Windows Server 2003

Resolution


Hotfix information

Note Install this hotfix on all computers in the cluster.


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

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.
Windows Server 2003, 32-bit versions
   Date         Time   Version       Size     File name
-----------------------------------------------------
02-Dec-2004 21:36 5.2.3790.239 111,616 Ksecdd.sys
02-Dec-2004 22:19 5.2.3790.238 130,048 Msv1_0.dll

Windows Server 2003, Enterprise Edition for Itanium-based Systems
   Date         Time   Version       Size     File name   Platform
---------------------------------------------------------------
02-Dec-2004 21:46 5.2.3790.239 257,536 Ksecdd.sys
02-Dec-2004 22:19 5.2.3790.238 342,016 Msv1_0.dll IA-64
02-Dec-2004 22:19 5.2.3790.238 130,048 Wmsv1_0.dll x86

Workaround


To work around this problem, remove the NTLM version 2 (NTLMv2) requirement from the security policies. To do this, follow these steps:
  1. Click Start, point to Administrative Tools, and then click Domain Security Policy.
  2. Expand the Local Policies subtree, and then click Security Options.
  3. Double-click Network security: Minimum session security for NTLM SSP based (including secure RPC) clients.
  4. Click to clear the Require NTLMv2 session security check box, and then click OK.
  5. Double-click Network security: Minimum session security for NTLM SSP based (including secure RPC) servers.
  6. Click to clear the Require NTLMv2 session security check box, and then click OK.
NoteWe recommend that you restart both nodes after you modify any one of the security policy settings.

To verify that the Cluster service account has the correct permissions, click the following article number to view the article in the Microsoft Knowledge Base:
269229 How to manually re-create the Cluster service account

Status


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

References


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

824684 Description of the standard terminology that is used to describe Microsoft software updates