FIX: Cluster resource fails to come online on IBM Netfinity with Windows 2000 (266060)

SYMPTOMS

After you configure a Microsoft Message Queuing cluster resource on a Windows 2000-based computer, the Message Queuing cluster resource fails to come online and logs an event that states no disk resource was found.

CAUSE

The Message Queuing cluster resource code checks for a Resource Type Name of "Physical Disk" the first time the resource is brought online after it has been configured. Some vendors supply their own cluster resource DLLs for shared disk resource types, and use a Resource Type Name other than "Physical Disk." IBM Netfinity with the IBM ServeRAID controller supplies its own cluster resource DLL, which creates a value of "IBM ServeRAID Logical Disk" instead of "Physical Disk." For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

256628 How to Install Clustering on a SCSI IBM Server

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date       Time    Version  Size   File name   Platform
   -----------------------------------------------------------
   10/31/2000 9:59AM  715      49,424 Mqclus.dll  Windows 2000

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

MORE INFORMATION

This fix changes the Message Queuing Resource DLL so that it checks the Resource Type instead of the Resource Type Name. Regardless of the Resource Type Name that a vendor uses in their resource DLL, the Resource Type must correspond to those defined by MSCS.

After you install Message Queuing, apply this fix before bringing the Message Queuing cluster resource online.