Help and Support

Article ID: 923838 - Last Review: October 30, 2006 - Revision: 1.4

Cannot start the Cluster Service and Event IDs 1009 and 7031 are logged on a computer that is running Windows Server 2003 or Windows 2000 Server

View products that this article applies to.

On This Page

Expand all | Collapse all

SYMPTOMS

When you try to create a new server cluster or use the Cluster Administrator tool

Microsoft Windows Server 2003

When you try to create a new Microsoft Windows Server 2003-based server cluster on a computer that is running Windows Server 2003, you may experience the following symptoms:
  • You receive the following error message when you try to start the Cluster service:
    Could not start the cluster service on local computer. Error 1067: The process terminated unexpectedly. Could not start the cluster service on local computer.

    Error 1067: The process terminated unexpectedly.
  • The following events are logged in the System log:

    Event ID 1009

    Event Type: Error
    Event Source: ClusSvc
    Event Category: Startup/Shutdown
    Event ID: 1009
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: Cluster service could not join an existing server cluster and could not form a new server cluster. Cluster service has terminated.

    Data: 0000: 000013de

    Event ID 7031

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7031
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

  • Information that resembles the following is logged in the %Wiindir%\Cluster\Cluster.log file:
    29c:198.03/02[16:20:26.320](000756) ERR  [FM] Arbitrate for quorum resource id 37fa028a-b2b9-4e9d-adb3-9bf69700f803.
29c:198.03/02[16:20:26.320](000756) INFO [FM] Initializing resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 from the registry.
29c:198.03/02[16:20:26.320](000756) INFO [FM] Name for Resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 is 'Disk R:'.
29c:198.03/02[16:20:26.320](000756) INFO [FM] FmpRmCreateResource: creating resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 in shared resource monitor
160:624.03/02[16:20:26.480](000756) INFO Physical Disk <Disk R:>: [DiskArb] ArbitrationInfoCleanup.
160:624.03/02[16:20:26.480](000756) ERR  Physical Disk <Disk R:>: Cannot open a handle to clusdisk driver, c0000034.
160:624.03/02[16:20:26.480](000756) WARN [RM] RmpInsertResourceList failed, returned 3221225524
160:624.03/02[16:20:26.480](000756) ERR  [RM] Failed creating resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803, error 3221225524.
29c:198.03/02[16:20:26.480](000756) INFO [FM] FmpRmCreateResource: unable to create resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803
29c:198.03/02[16:20:26.480](000756) WARN [FM] Error completing initialization of quorum resource '37fa028a-b2b9-4e9d-adb3-9bf69700f803, error 3221225524.
29c:198.03/02[16:20:26.490](000756) ERR  [FM] FmGetQuorumResource failed, error 3221225524.
29c:198.03/02[16:20:26.490](000756) ERR  [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
29c:198.03/02[16:20:26.490](000756) INFO [INIT] Cleaning up failed form attempt.
29c:198.03/02[16:20:26.490](000756) ERR  [INIT] Failed to form cluster, status 5086.
160:7fc.03/02[16:20:26.490](000756) ERR  [RM] Exception. Code = 0xc0000005, Address = 0x6EB5FC1F
160:7fc.03/02[16:20:26.490](000756) ERR  [RM] Exception parameters: 0, 6eb5fc1f, 1003f, 0
29c:198.03/02[16:20:26.681](000756) ERR  [CS] ClusterInitialize failed 5086
29c:198.03/02[16:20:26.681](000756) WARN [INIT] The cluster service is shutting down.
29c:198.03/02[16:20:26.681](000756) INFO [EVT] EvShutdown
29c:198.03/02[16:20:26.681](000756) WARN [FM] Shutdown: Failover Manager requested to shutdown groups.
29c:198.03/02[16:20:26.681](000756) INFO [FM] FmpCleanupGroups: Entry
29c:198.03/02[16:20:26.681](000756) INFO [FM] FmpCleanupGroups: Exit
29c:198.03/02[16:20:26.681](000756) INFO [Dm] DmShutdown
29c:198.03/02[16:20:26.681](000756) INFO [DM] DmpShutdownFlusher: Entry
29c:198.03/02[16:20:26.681](000756) INFO [DM] DmpShutdownFlusher: Setting event
29c:1a0.03/02[16:20:26.681](000756) INFO [DM] DmpRegistryFlusher: got 0
29c:1a0.03/02[16:20:26.681](000756) INFO [DM] DmpRegistryFlusher: exiting
29c:198.03/02[16:20:26.691](000756) WARN [MM] MMLeave is called when rgp=NULL.
29c:198.03/02[16:20:26.691](000756) ERR  [CS] Service Stopped. exit code = 5086
Additionally, you may experience a problem with the Cluster Administrator tool. Consider the following scenario. On a computer that is running Windows Server 2003, you start the Cluster service together with the /fixquorum switch. Then, you perform tasks by using the Cluster Administrator tool. In this scenario, you experience the following symptoms:
  • You receive the following error message:
    An error occurred attempting to read properties for the 'Disk Q' resource.
    Object Name not found. Error ID: -1073741772 (c0000034).
  • You receive the following error message when you try to bring the disk resource online:
    No possible owners are specified for this resource, which means that this resource cannot be brought online on any node in the cluster. This could be caused by the resource DLL for this type of resource not being installed on at least one node in the cluster.
  • When you right-click a disk resource, and then click Properties, the Advanced tab and the Parameters tab are unavailable (appear dimmed).
  • When you try to move a disk resource, the following event is logged in the System log:

    Event Type: Information
    Event Source: ClusSvc
    Event Category: Failover Mgr
    Event ID: 1205
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service failed to bring the Resource Group "Group 0" completely online or offline.

    Also, the following information is logged in the %Windir%\Cluster\Cluster.log file:
    6b4:648.03/02[16:29:16.993](000006) INFO [FM] FmpRmCreateResource: unable to create resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803
6b4:684.03/02[16:29:43.161](000006) INFO [FM] FmpRmCreateResource: creating resource b568b68c-2065-4fa6-b55c-5c469728325f in shared resource monitor
1ac:600.03/02[16:29:43.171](000006) INFO Physical Disk <Disk S:>: [DiskArb] ArbitrationInfoCleanup.
1ac:600.03/02[16:29:43.171](000006) ERR  Physical Disk <Disk S:>: Cannot open a handle to clusdisk driver, c0000034.
1ac:600.03/02[16:29:43.171](000006) WARN [RM] RmpInsertResourceList failed, returned 3221225524
1ac:600.03/02[16:29:43.171](000006) ERR  [RM] Failed creating resource b568b68c-2065-4fa6-b55c-5c469728325f, error 3221225524.

Microsoft Windows 2000 Server

When you try to create a new Microsoft Windows 2000-based server cluster on a computer that is running Windows 2000, you may experience the following symptoms:
  • You receive the following error message when you try to start the Cluster service:
    Windows could not start the cluster service on local Computer.

    For more information, review the System Event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5086.
  • The following events are logged in the System log:

    Event ID 1058

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (2048)
    Event ID: 1058
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster Resource Monitor could not load the DLL clusres.dll for resource type Physical Disk.

    Data: 0000: 0000045a

    Event ID 1009

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (128)
    Event ID: 1009
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Clustering Service could not join an existing cluster and could not form a new cluster. The Clustering Service has terminated.
    Data: 0000: 000013de

    Event ID 7031

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7031
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: No action

  • Information that resembles the following is logged in the %Windir%\Cluster\Cluster.log file:
    634:4c8.03/02[13:35:57.356](007488) [FM] FmpRmCreateResource: creating resource 4342ab06-9a56-4afe-b181-b030a381d359 in shared resource monitor
748:68c.03/02[13:35:59.709](007488) [RM] Error loading resource dll clusres.dll, error 1114.
748:68c.03/02[13:35:59.859](007488) [RM] CLSIDFromProgID clusres.dll, hr = 2147746291.
748:68c.03/02[13:35:59.859](007488) [RM] CLSIDFromString Also failed clusres.dll, hr = 2147746291.
748:68c.03/02[13:35:59.859](007488) [RM] Error loading resource dll clusres.dll, error 1114.
748:68c.03/02[13:35:59.920](007488) [RM] Failed creating resource 4342ab06-9a56-4afe-b181-b030a381d359, error 1114.
634:4c8.03/02[13:35:59.920](007488) [FM] FmpRmCreateResource: unable to create resource 4342ab06-9a56-4afe-b181-b030a381d359
634:4c8.03/02[13:35:59.920](007488) [FM] Error completing initialization of quorum resource '4342ab06-9a56-4afe-b181-b030a381d359, error 1114.
634:4c8.03/02[13:35:59.920](007488) [FM] FmGetQuorumResource failed, error 1114.
634:4c8.03/02[13:35:59.920](007488) [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
634:4c8.03/02[13:35:59.920](007488) [INIT] Cleaning up failed form attempt.
634:4c8.03/02[13:35:59.920](007488) [INIT] Failed to form cluster, status 5086.
634:4c8.03/02[13:35:59.920](007488) [CS] ClusterInitialize failed 5086
634:4c8.03/02[13:35:59.970](007488) [INIT] The cluster service is shutting down.
Additionally, you may experience a problem with the Cluster Administrator tool. Consider the following scenario. On a computer that is running Windows 2000 Server, you start the Cluster service together with the /fixquorum switch. In this scenario, you experience the following symptoms:
  • Events that resemble the following are logged in the System log one time for each resource:

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (2048)
    Event ID: 1058
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster Resource Monitor could not load the DLL clusres.dll for resource type IP Address.
    Data: 0000: 0000045a

  • Error information that resembles the following is logged in the %Windir%\Cluster\Cluster.log file:
    754:438.03/02[13:45:38.634](007487) [FM] Preferred owners list is now empty! No place to run group a3003e00-4dda-4276-9c69-c0192b97c2e2
760:770.03/02[13:45:40.437](007487) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
760:770.03/02[13:45:40.808](007487) [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
760:770.03/02[13:45:40.808](007487) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
760:788.03/02[13:45:43.221](007498) [RM] Error loading resource dll clusres.dll, error 1114.
760:788.03/02[13:45:43.221](007498) [RM] Failed creating resource b8177d64-70f5-4655-b0af-487d674b2e08, error 1114.
760:770.03/02[13:45:43.231](007498) [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
760:770.03/02[13:45:43.231](007498) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
  • When you start the Cluster Administrator program, you receive one of the following error messages:
    An error occurred attempting to read properties for the 'File Share' resource type:
    Invalid class string
    Error ID: -2147221005 (800401f3).
    An error occurred attempting to read properties for the 'Disk Q:' resource:
    A dynamic link library (DLL) initialization routine failed.
    Error ID: 1114 (0000045a)
  • When you try to bring a disk resource online by using the Cluster Administrator tool, you receive the following error message:
    No possible owners are specified for this resource. This means that this resource cannot be brought online on any node in the cluster.
Back to the top

When you try to create or to manage a server cluster

Microsoft Windows Server 2003

When you try to create a server cluster
You experience the following symptoms when you try to create a new Windows Server 2003-based server cluster:
  • You receive the following error message when you try to start the Cluster service:
    Could not start the cluster service on local computer. Error 1067: The process terminated unexpectedly. Could not start the cluster service on local computer.

    Error 1067: The process terminated unexpectedly.
  • The following events are logged in the System log:

    Event ID 1009

    Event Type: Error
    Event Source: ClusSvc
    Event Category: Startup/Shutdown
    Event ID: 1009
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: Cluster service could not join an existing server cluster and could not form a new server cluster. Cluster service has terminated.

    Data: 0000: 000013de

    Event ID 7031

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7031
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

  • Information that resembles the following is logged in the %WINDIR%\Cluster\cluster.log file:
    29c:198.03/02[16:20:26.320](000756) ERR  [FM] Arbitrate for quorum resource id 37fa028a-b2b9-4e9d-adb3-9bf69700f803.
29c:198.03/02[16:20:26.320](000756) INFO [FM] Initializing resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 from the registry.
29c:198.03/02[16:20:26.320](000756) INFO [FM] Name for Resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 is 'Disk R:'.
29c:198.03/02[16:20:26.320](000756) INFO [FM] FmpRmCreateResource: creating resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803 in shared resource monitor
160:624.03/02[16:20:26.480](000756) INFO Physical Disk <Disk R:>: [DiskArb] ArbitrationInfoCleanup.
160:624.03/02[16:20:26.480](000756) ERR  Physical Disk <Disk R:>: Cannot open a handle to clusdisk driver, c0000034.
160:624.03/02[16:20:26.480](000756) WARN [RM] RmpInsertResourceList failed, returned 3221225524
160:624.03/02[16:20:26.480](000756) ERR  [RM] Failed creating resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803, error 3221225524.
29c:198.03/02[16:20:26.480](000756) INFO [FM] FmpRmCreateResource: unable to create resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803
29c:198.03/02[16:20:26.480](000756) WARN [FM] Error completing initialization of quorum resource '37fa028a-b2b9-4e9d-adb3-9bf69700f803, error 3221225524.
29c:198.03/02[16:20:26.490](000756) ERR  [FM] FmGetQuorumResource failed, error 3221225524.
29c:198.03/02[16:20:26.490](000756) ERR  [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
29c:198.03/02[16:20:26.490](000756) INFO [INIT] Cleaning up failed form attempt.
29c:198.03/02[16:20:26.490](000756) ERR  [INIT] Failed to form cluster, status 5086.
160:7fc.03/02[16:20:26.490](000756) ERR  [RM] Exception. Code = 0xc0000005, Address = 0x6EB5FC1F
160:7fc.03/02[16:20:26.490](000756) ERR  [RM] Exception parameters: 0, 6eb5fc1f, 1003f, 0
29c:198.03/02[16:20:26.681](000756) ERR  [CS] ClusterInitialize failed 5086
29c:198.03/02[16:20:26.681](000756) WARN [INIT] The cluster service is shutting down.
29c:198.03/02[16:20:26.681](000756) INFO [EVT] EvShutdown
29c:198.03/02[16:20:26.681](000756) WARN [FM] Shutdown: Failover Manager requested to shutdown groups.
29c:198.03/02[16:20:26.681](000756) INFO [FM] FmpCleanupGroups: Entry
29c:198.03/02[16:20:26.681](000756) INFO [FM] FmpCleanupGroups: Exit
29c:198.03/02[16:20:26.681](000756) INFO [Dm] DmShutdown
29c:198.03/02[16:20:26.681](000756) INFO [DM] DmpShutdownFlusher: Entry
29c:198.03/02[16:20:26.681](000756) INFO [DM] DmpShutdownFlusher: Setting event
29c:1a0.03/02[16:20:26.681](000756) INFO [DM] DmpRegistryFlusher: got 0
29c:1a0.03/02[16:20:26.681](000756) INFO [DM] DmpRegistryFlusher: exiting
29c:198.03/02[16:20:26.691](000756) WARN [MM] MMLeave is called when rgp=NULL.
29c:198.03/02[16:20:26.691](000756) ERR  [CS] Service Stopped. exit code = 5086
Cluster Administrator errors
You experience the following symptoms when you perform tasks by using the Cluster Administrator tool after you start the Cluster service together with the /fixquorum switch:
  • You receive the following error message:
    An error occurred attempting to read properties for the 'Disk Q' resource.
    Object Name not found. Error ID: -1073741772 (c0000034).
  • You receive the following error message when you try to bring the disk resource online:
    No possible owners are specified for this resource, which means that this resource cannot be brought online on any node in the cluster. This could be caused by the resource DLL for this type of resource not being installed on at least one node in the cluster.
  • When you right-click a disk resource, and then click Properties, the Advanced tab and the Parameters tab are unavailable (appear dimmed).
  • When you try to move a disk resource, the following event is logged in the System log:

    Event Type: Information
    Event Source: ClusSvc
    Event Category: Failover Mgr
    Event ID: 1205
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service failed to bring the Resource Group "Group 0" completely online or offline.

    Also, the following information is logged in the %WINDIR%\Cluster\cluster.log file:
    6b4:648.03/02[16:29:16.993](000006) INFO [FM] FmpRmCreateResource: unable to create resource 37fa028a-b2b9-4e9d-adb3-9bf69700f803
6b4:684.03/02[16:29:43.161](000006) INFO [FM] FmpRmCreateResource: creating resource b568b68c-2065-4fa6-b55c-5c469728325f in shared resource monitor
1ac:600.03/02[16:29:43.171](000006) INFO Physical Disk <Disk S:>: [DiskArb] ArbitrationInfoCleanup.
1ac:600.03/02[16:29:43.171](000006) ERR  Physical Disk <Disk S:>: Cannot open a handle to clusdisk driver, c0000034.
1ac:600.03/02[16:29:43.171](000006) WARN [RM] RmpInsertResourceList failed, returned 3221225524
1ac:600.03/02[16:29:43.171](000006) ERR  [RM] Failed creating resource b568b68c-2065-4fa6-b55c-5c469728325f, error 3221225524.

Microsoft Windows 2000 Server

When you try to create a server cluster
You experience the following symptoms when you try to create a new Windows 2000-based server cluster:
  • You receive the following error message when you try to start the Cluster service:
    Windows could not start the cluster service on local Computer.

    For more information, review the System Event log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5086.
  • The following events are logged in the System log:

    Event ID 1058

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (2048)
    Event ID: 1058
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster Resource Monitor could not load the DLL clusres.dll for resource type Physical Disk.

    Data: 0000: 0000045a

    Event ID 1009

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (128)
    Event ID: 1009
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Clustering Service could not join an existing cluster and could not form a new cluster. The Clustering Service has terminated.
    Data: 0000: 000013de

    Event ID 7031

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7031
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: No action

  • Information that resembles the following is logged in the %WINDIR%\Cluster\cluster.log file:
    634:4c8.03/02[13:35:57.356](007488) [FM] FmpRmCreateResource: creating resource 4342ab06-9a56-4afe-b181-b030a381d359 in shared resource monitor
748:68c.03/02[13:35:59.709](007488) [RM] Error loading resource dll clusres.dll, error 1114.
748:68c.03/02[13:35:59.859](007488) [RM] CLSIDFromProgID clusres.dll, hr = 2147746291.
748:68c.03/02[13:35:59.859](007488) [RM] CLSIDFromString Also failed clusres.dll, hr = 2147746291.
748:68c.03/02[13:35:59.859](007488) [RM] Error loading resource dll clusres.dll, error 1114.
748:68c.03/02[13:35:59.920](007488) [RM] Failed creating resource 4342ab06-9a56-4afe-b181-b030a381d359, error 1114.
634:4c8.03/02[13:35:59.920](007488) [FM] FmpRmCreateResource: unable to create resource 4342ab06-9a56-4afe-b181-b030a381d359
634:4c8.03/02[13:35:59.920](007488) [FM] Error completing initialization of quorum resource '4342ab06-9a56-4afe-b181-b030a381d359, error 1114.
634:4c8.03/02[13:35:59.920](007488) [FM] FmGetQuorumResource failed, error 1114.
634:4c8.03/02[13:35:59.920](007488) [INIT] ClusterForm: Could not get quorum resource. No fixup attempted. Status = 5086
634:4c8.03/02[13:35:59.920](007488) [INIT] Cleaning up failed form attempt.
634:4c8.03/02[13:35:59.920](007488) [INIT] Failed to form cluster, status 5086.
634:4c8.03/02[13:35:59.920](007488) [CS] ClusterInitialize failed 5086
634:4c8.03/02[13:35:59.970](007488) [INIT] The cluster service is shutting down.
Cluster Administrator errors
After you start the Cluster service together with the /fixquorum switch, you experience the following symptoms:
  • Events that resemble the following are logged in the System log one time for each resource:

    Event Type: Error
    Event Source: ClusSvc
    Event Category: (2048)
    Event ID: 1058
    Date: date
    Time: time
    User: N/A
    Computer: computername
    Description: The Cluster Resource Monitor could not load the DLL clusres.dll for resource type IP Address.
    Data: 0000: 0000045a

  • Error information that resembles the following is logged in the %WINDIR%\Cluster\cluster.log file:
    754:438.03/02[13:45:38.634](007487) [FM] Preferred owners list is now empty! No place to run group a3003e00-4dda-4276-9c69-c0192b97c2e2
760:770.03/02[13:45:40.437](007487) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
760:770.03/02[13:45:40.808](007487) [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
760:770.03/02[13:45:40.808](007487) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
760:788.03/02[13:45:43.221](007498) [RM] Error loading resource dll clusres.dll, error 1114.
760:788.03/02[13:45:43.221](007498) [RM] Failed creating resource b8177d64-70f5-4655-b0af-487d674b2e08, error 1114.
760:770.03/02[13:45:43.231](007498) [RM] ResTypeControl: Error loading resource DLL 'clusres.dll, error 1114.
760:770.03/02[13:45:43.231](007498) [RM] Error converting CLSIDFromProgID Prog ID clusres.dll, error 2147746291.
  • When you start the Cluster Administrator program, you receive one of the following error messages:

    Error message 1
    An error occurred attempting to read properties for the 'File Share' resource type:
    Invalid class string
    Error ID: -2147221005 (800401f3).
    Error message 2
    An error occurred attempting to read properties for the 'Disk Q:' resource:
    A dynamic link library (DLL) initialization routine failed.
    Error ID: 1114 (0000045a)
  • When you try to bring a disk resource online by using the Cluster Administrator tool, you receive the following error message:
    No possible owners are specified for this resource. This means that this resource cannot be brought online on any node in the cluster.
Back to the top

CAUSE

This problem occurs if the Cluster Disk driver (Clusdisk.sys) is not running.

You may stop the Clusdisk.sys driver together with the Cluster service when you troubleshoot an underlying hard disk subsystem problem. If you do not restart the Clusdisk.sys driver after you finish troubleshooting the disk subsystem problem, the cluster does not function correctly.
Back to the top

RESOLUTION

To resolve this problem, start the Clusdisk.sys driver and set its startup type to System. To do this, follow these steps:
  1. Stop the Cluster service, and then configure it to use the Manual startup type. To do this, follow these steps:
    1. Click Start, click Run, type services.msc, and then click OK.
    2. In Services, right-click Cluster service, and then click Properties.
    3. In the Cluster service Properties (Local Computer) dialog box, click Stop.
    4. In the Startup type list, click Manual, and then click OK.
  2. Start Device Manager. To do this, click Start, click Run, type devmgmt.msc, and then click OK.
  3. On the View menu, click Show hidden devices if this command is not already selected.
  4. Expand Non-Plug and Play Drivers, right-click Cluster Disk Driver, and then click Properties.
  5. In the Cluster Disk Driver Properties dialog box, click the Driver tab.
  6. In the Type list, click System, click Start, verify that the Started appears next to Status, and then click OK.
  7. In Services, set the Cluster service startup type to Automatic, and then start the Cluster service.
Back to the top
APPLIES TO
  • Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
  • Microsoft Windows Server 2003 R2 Enterprise x64 Edition
  • Microsoft Windows Server 2003 R2 Datacenter x64 Edition
  • 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
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
Back to the top
Keywords: 
kbclustering kbtshoot kberrmsg kbprb KB923838
Back to the top

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers