When a clustered Generic Service resource stops, the service associated with the resource is not stopped

Applies to: Windows Server 2008 DatacenterWindows Server 2008 EnterpriseWindows Server 2008 R2 Datacenter


Consider the following scenario:
  • One or more Generic Service resources are configured on a Windows Server 2008-based or Windows Server 2008 R2-based cluster.
  • The Resource Monitor process (Rhs.exe) that is associated with the clustered Generic Service resource is restarted. This restart stops the resource.
A service of the clustered Generic Service resource is not stopped when the Generic Service resource is stopped. Therefore, the service is still running on the passive node even after the failover occurs.


When the Rhs.exe is restarted, the Rhs.exe does not reinitialize the handle for the service. Therefore, Rhs.exe cannot stop the service when the resource is stopped.


To work around this problem, create a dedicated Rhs.exe process for the clustered Generic Service resource. This dedicated process is not restarted when other resources fail to start.

To implement this configuration, follow these steps:
  1. Open the Failover Cluster Management console.
  2. Under Services and applications, select the clustered application that owns the affected generic service.
  3. Select the affected generic service resource from the middle pane, and open its properties.
  4. Click the Advanced Policies tab.
  5. Click to select the Run this resource in a separate Resource Monitor check box.
  6. Click OK to confirm the new settings.
Note This workaround cannot be used when the dedicated Rhs.exe process is restarted. In this case, you have to stop the service manually.

More Information

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.