The Cluster Service May Start Even Though the Cluster Disk Driver Is Set to Demand (299041)



The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server

This article was previously published under Q299041

SYMPTOMS

The Cluster service may start on a cluster node even if the cluster disk driver is set to demand (manual). All cluster resources are online on other nodes in the cluster, and a connection can be made to the cluster by using the Cluster Administrator tool (CluAdmin.exe) provided that the properly configured node owns the cluster group. If a connection is made to the Cluster service that is running on the local node by connecting to the period symbol (.) in Cluster Administrator (for example, you run "cluadmin ."), you may receive the following error message:
An error occurred attempting to read properties for "File Share" resource type. Invalid class string
Error ID: -2147221005 {800401f3}
Do you want to continue?
NOTE: This message can be displayed for each resource that uses the Clusres.dll file.

All cluster resource types that are supported by Clusres.dll may be unsuccessful in their attempts to initialize properly. If a resource failure occurs on another node and an attempt is made to move resources to the node where the cluster disk driver is not started, you may receive the following error message:
An error occurred attempting to move the "Group Name" group: A cluster node is not available for this operation. Error ID: 5005 {0000138d}
This message is displayed even if the Cluster service is started on the node where the cluster disk driver is set to demand. If the message does not display, and the resource group includes the quorum disk, the quorum drive and all the resources in the group can undergo a transition to an offline state. At that point the cluster is no longer available and manual intervention is required to restart the Cluster service after you start the cluster disk driver.

The following error message may be logged in the System event log:
Event ID 1058 for clussvc Category [2048] The cluster resource monitor could not load the Clusres.dll for resource type "xxxxxxx" (where xxxxxx corresponds to each resource type previously mentioned above).
Also, the following entries may be logged in the cluster log:
000004cc.000004e4::2001/05/15-17:00:53.187 [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
000004cc.000004e4::2001/05/15-17:00:53.187 [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
000004cc.000004ec::2001/05/15-17:02:17.328 [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
000004cc.000004ec::2001/05/15-17:02:17.328 [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
000004cc.000004d8::2001/05/15-17:02:32.484 [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
000004cc.000004d8::2001/05/15-17:02:32.484 [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
00000430.000005bc::2001/05/15-17:02:42.203 [FM] FmpSetPossibleNodeForResType: for type IIS Server Instance, bAssumeSupported= 1.

CAUSE

This problem can occur because the cluster disk driver is set to demand and the Cluster service does not verify if the cluster disk driver has started prior to starting the Cluster service.

RESOLUTION

To resolve this problem, manually start the cluster disk driver and set the Startup value to "System."

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION


Modification Type:MinorLast Reviewed:1/27/2006
Keywords:kbClustering kbprb w2000mscs KB299041