You receive a "0x00138f Cluster resource not found" error message when you try to join a second node to a Windows Server 2003 cluster (909968)


The information in this article applies to:

  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise x64 Edition

SYMPTOMS

When you try to join a second node to a Microsoft Windows Server 2003 cluster, you receive the following error message:
0x00138f Cluster resource not found

CAUSE

This issue occurs in a complex storage area network (SAN) configuration.

This issue is caused by an interaction between two technologies: the new Cluster Setup Wizard and the SAN configuration. The new Cluster Setup Wizard contains heuristics to verify that all cluster nodes have access to the same disks. To perform this verification, the wizard determines whether all cluster nodes recognize the disks that use the same target ID (TID) and the same logical unit number (LUN). Typically, the wizard can successfully perform this verification when a cluster shared-disk array is configured correctly. However, with a complex SAN configuration, the wizard may not be able to perform this verification.

In a complex SAN environment, the "0x00138f Cluster resource not found" error message may indicate that the same set of disks have been detected on different TIDs and on different LUNs by individual nodes. In this scenario, Setup matches the resource name to verify that all cluster nodes have access to the same disk. Then, the setup process continues.

WORKAROUND

To work around this issue, let the Cluster Setup Wizard process continue. The second node does eventually join the cluster.

MORE INFORMATION

A SAN that has multiple switches between the nodes and the storage component is an example of a complex storage solution. Because the cluster nodes do not require that the same path for any particular disk always be used, nodes may enumerate the disks by using different IDs. For example, node A may enumerate disk 1 as follows:

LUN 1 TID 1

However, because node B can be connected to a separate switch and to a separate controller in the SAN and still enumerate the same disk, the disk may be enumerated as follows:

LUN 2 TID 3

You may also receive the error that is mentioned in the "Symptoms" section if you use multi-pathing software. You may receive the error message when the multi-pathing software runs an analysis phase where the request could go down one path. Next, the multi-pathing software runs a commit phase where the request could go down another path. Because the first "Bus / Port / TID / LUN" query and the second "Bus / Port / TID / LUN" query do not match, you may receive the error message that is mentioned in the "Symptoms" section.
Modification Type:MajorLast Reviewed:2/2/2006
Keywords:kbExpertiseAdvanced kbtshoot kberrmsg KB909968 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.