大网数据广告活动
故障转移群集

Cluster Service Stops Responding

· 52CE 我爱测

Provides a resolution for the issue that Cluster Service stops responding on a Cluster Node when you restart the Active Node.

This article provides a resolution for the issue that Cluster Service stops responding on a Cluster Node when you restart the Active Node.

Original KB number:   822050

Symptoms

When you restart the active node of a server cluster that consists of two or more nodes, you experience all the following symptoms:

  • If you are running Cluster Administrator on the remaining nodes, you receive the following error message when you try to connect to the cluster:

    Cluster 'ClusterName' is no longer available.

  • If you try to start Cluster Administrator, Cluster Administrator stops responding, and you may receive the following error message:

    An error occurred trying to open the cluster at 'ServerName':

    The interface is unknown.

    Error ID: 1717 (000006b5).

  • When you view the contents of C:\Winnt\ Cluster.log, you see information similar to:

    [FM] OnlineGroup: Failed on resource e3f4af72-6454-4199-b9af-fa6f57032a65. Status 70
    Microsoft Clustering Service suffered an unexpected fatal error
    at line 701 of source module D:\nt\private\cluster\service\fm\group.c. The error code was 70.

  • When the restarted cluster node starts successfully, the Cluster Administrator program that is running on the other nodes responds as you expect.

Cause

This issue occurs if you pause one node of a server cluster and then you restart the active cluster node. When the active node restarts, the paused node tries to bring resource groups online. Because this node is paused, the node cannot make additional connections, and it cannot bring the Quorum disk group online. Error code 70 corresponds to the following error message:

The remote server has been paused or is in the process of being started.

Note: These results will also occur in clusters that have more than two nodes. Even though a non-paused node exists in a working state when the active node is restarted, if the paused node is the first node that is contacted to take ownership of the quorum disk. The non-paused node does not have the opportunity to arbitrate for the quorum disk.

Resolution

To resolve this issue, resume the paused cluster node before you restart the active cluster node.

Note: Before you resume a paused cluster node, you must first determine if a cluster node is paused.

  1. Click Start, click Run, type cmd in the Open box, and then click OK.

  2. At the command prompt, type cluster node, and then press ENTER. Output is similar to:

    [!NOTE] The following sample output is based on a two-node cluster configuration. If you have more than two nodes, the additional nodes will also appear in the list.

    Node    Node ID  Status
    -------------- --------- ---------------------
    CLUSTER-1    1   Paused
    CLUSTER-2    2   Up

    [!NOTE] If the only cluster node that is not paused is in the process of restarting, you receive the following error message:
    System error 1753 has occurred. There are no more endpoints available from the endpoint mapper.

  3. At the command prompt, type cluster node node_name /resume (where node_name is the name of the cluster node) and then press ENTER.

    For example, type cluster node cluster-1 /resume, and then press ENTER. Information appears that is similar to:

    Resuming node 'cluster-1'...

    Node     Node ID   Status
    --------------  ---------   ---------------------
    CLUSTER-1     1    Up

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。