Microsoft KB Archive/923840

= You cannot add an additional node to a Windows Server 2003-based server cluster, and error code &quot;0x8007042b&quot; is logged in the ClCfgSrv.log file =

Article ID: 923840

Article Last Modified on 5/24/2007

-

APPLIES TO


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

-





SYMPTOMS
When you try to add an additional node to a Microsoft Windows Server 2003-based server cluster, you experience the following symptoms:  The following errors appear on the Adding Nodes to the Cluster page of the Add Nodes Wizard:

Under Reanalyzing cluster

Status 0x00138f: The cluster resource could not be found.

Under Configure cluster services

Error 0x8007042b: The process terminated unexpectedly.

 The following information is logged in the %WINDIR%\system32\LogFiles\Cluster\ClCfgSrv.log file:

 [INFO] [MT] [CTaskCommitClusterChanges] Exiting task. The task was not cancelled. (hr = 0x8007042b) [INFO] [BC] A runtime error has occurred in file ' \cservice.cpp', line 417. Error code is 0x8007042b. [ERR ] erpbatch1: A problem occurred when the wizard attempted to start a service. (hr=0x8007042b, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B}, {3ABE1494-7E05-402C-81AA-1C3F1D782031}, 1, 1, 1),

 The following information is logged in the %WINDIR%\Cluster\Cluster.log file:

000003b8.00000f9c:: .022 WARN [INIT] Failed to join cluster, status 5010 000003b8.00000f9c:: .022 ERR  [CS] ClusterInitialize failed 5010 000003b8.00000f9c:: .006 ERR  [NM] Failed to configure networks & interfaces, status 5010. 000003b8.00000f9c:: .474 WARN [NMJOIN] Failed to read cluster instance ID from database, status 2.

000003b8.00000f9c:: .022 ERR  [CS] Service Stopped. exit code = 5010





CAUSE
This issue occurs if the network settings are configured incorrectly on the computer that you want to add to the server cluster. Specifically, this issue occurs if the network adapter on which the private cluster communications is intended to occur has a different subnet mask than that of the network adapter on the computer that is a member of the cluster.

Consider the following examples of mismatched network settings. In these examples, computer 1 is assigned a class B subnet mask, and computer 2 is assigned a class C subnet mask. Therefore, the two private network adapters have mismatched subnet mask settings.

Computer 2: To be added to the server cluster


RESOLUTION
To resolve this issue, verify the network settings on the computer that you want to add to the server cluster. Configure the subnet mask on each network adapter to match the subnet mask of the corresponding network adapter on the computer that is already a member of the server cluster.

To view the network settings in Windows Server 2003, follow these steps:
 * 1) Click Start, click Run, type ncpa.cpl, and then click OK.
 * 2) In the Network Connections dialog box, right-click a network connection, and then click Properties.
 * 3) Click Internet Protocol (TCP/IP), and then click Properties.
 * 4) Type the correct subnet mask in the Subnet mask box, click OK, and then click Close.



MORE INFORMATION
For more information about Windows Server 2003 Clustering Services, visit the following Microsoft Web sites:

http://www.microsoft.com/windowsserver2003/techinfo/overview/clustering.mspx

http://www.microsoft.com/windowsserver2003/enterprise/clustering.mspx

Additional query words: MSCS

Keywords: kbclustering kbtshoot kbprb KB923840

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.