locked
Cannot Start Failover Cluster

    Question

  • Error:
    Failed to create cluster, failed to create cluster ip address. 
    Event: Cluster resource 'Cluster Name' (resource type '', DLL 'clusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.
    Followed by: The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor.

    Environment:
    2x 2008R2, Dell PE2950, added Intel quad NIC.
    same failures happen on both servers.

    Tried:
    Cluster Validation; succesfull.
    Switched to create single node cluster, also fails.
    Tried: http://support.microsoft.com/kb/973838, still fails.

    We have created a 4 node cluster with identical machines in the past. Only vLan is different, but I don't see how that might be the problem.

    Any suggestions?
    Monday, February 08, 2010 3:04 PM

Answers

All replies

  • Sollution found; Deleted WINS entry from WINS server for cluster name. Must have been there from previous failed attempt.

    Boy, egg on my face! The cluster destroyed itself overnight.

    And is now displaying the same behaviour as before.
    Monday, February 08, 2010 3:16 PM
  • Complete reinstall of both servers. Immediately after install created the cluster, this worked. Slowly added functions and LUNs. Still working great. Restarted this morning after installing DPM 2010 RC and it failed again. Uninstall did not fix the problem. Log Name: Application Source: Application Error Date: 15-2-2010 10:09:53 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: xxx Description: Faulting application name: rhs.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc489 Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b Exception code: 0xc0000005 Fault offset: 0x00000000000552c4 Faulting process id: 0x12a8 Faulting application start time: 0x01caae1e47e304d1 Faulting application path: C:\Windows\Cluster\rhs.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: e0451d31-1a11-11df-a983-001b212ee484
    Monday, February 15, 2010 10:25 AM
  • See this blog... the RHS crashes really aren't your problem, they are just a symptom:
    http://blogs.technet.com/askcore/archive/2009/11/23/resource-hosting-subsystem-rhs-in-windows-server-2008-failover-clusters.aspx

    What other errors / events are you seeing?
    • Marked as answer by Tim Quan Monday, February 22, 2010 6:51 AM
    • Unmarked as answer by Tim Quan Monday, February 22, 2010 6:51 AM
    • Marked as answer by Tim Quan Friday, February 26, 2010 8:22 AM
    Saturday, February 20, 2010 12:09 AM
    Owner
  • See this blog... the RHS crashes really aren't your problem, they are just a symptom:
    http://blogs.technet.com/askcore/archive/2009/11/23/resource-hosting-subsystem-rhs-in-windows-server-2008-failover-clusters.aspx

    What other errors / events are you seeing?
     

    Salved!

    Microsoft have released an hotfix:

    http://support.microsoft.com/kb/978527

     

    After installing the hotfix on both cluster nodes the problem was salved!
    • Marked as answer by Tim Quan Wednesday, March 24, 2010 1:25 AM
    Tuesday, March 23, 2010 12:30 PM