Microsoft KB Archive/890761

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

Article ID: 890761

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

-





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 1 Event Type: Error

Event Source: ClusSvc

Event Category: Membership Mgr

Event ID: 1173

Description:

Cluster service is shutting down because the membership engine detected a membership event while trying to join the server cluster. Shutting down is the normal response to this type of event. Cluster service will restart per the Service Manager's recovery actions.

Event message 2 Event Type: Error

Event Source: ClusSvc

Event Category: Startup/Shutdown

Event ID: 1073

Description:

Cluster service was halted to prevent an inconsistency within the server cluster. The error code was 5890.



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



Hotfix information
Note Install this hotfix on all computers in the cluster.

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Note We 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&quot;Applies to&quot; section.

