Knowledge

ERROR_CLUSTER_NODE_PAUSED - 5070 (0x13CE)

The cluster node is paused.

Updated: Feb 21, 2026

Technical Background

ERROR_CLUSTER_NODE_PAUSED is a specific error code in the Windows operating system, indicating that a cluster node has been paused. This condition can arise due to various reasons and affects the operation of clustered services and resources managed by the Windows Failover Clustering feature.

Error Details

The ERROR_CLUSTER_NODE_PAUSED error code (5070 or 0x13CE) is returned when a cluster node has been paused. This state can be manually initiated by an administrator or automatically triggered due to certain conditions, such as hardware failures, software issues, or maintenance activities.

Common Causes

  • Administrative Action: An administrator may have explicitly paused the node for maintenance or troubleshooting purposes.
  • Hardware Issues: Failures in hardware components, such as network interfaces or storage devices, can lead to a node being paused.
  • Software Problems: Software conflicts or bugs within the cluster management software might cause nodes to pause unexpectedly.

Real-World Context

In a Windows Failover Cluster environment, nodes are typically managed by the clusvc.exe service. When a node is paused, it stops participating in the cluster and ceases to manage resources. This can impact the availability of clustered services and applications that rely on the affected node.

Is This Error Critical?

The criticality of this error depends on the state of the cluster and the specific services running on the paused node. If multiple nodes are paused, it could lead to a degraded or failed cluster state, affecting the availability and reliability of clustered resources.

How to Diagnose

  1. Review Cluster Logs: Check the event logs for the clusvc service and any related cluster-related events that might indicate why the node was paused.
  2. Verify Node State: Use the clusvc.msc management console or PowerShell cmdlets like Get-ClusterNode to confirm the state of the node.
  3. Check Hardware Status: Ensure that all hardware components, such as network cards and storage devices, are functioning correctly.

How to Resolve

  1. Correct Parameter Usage: If the pause was due to incorrect parameters or settings, ensure they are corrected.
  2. Adjust Operation Context: If the node was paused due to an operational context issue, adjust the environment accordingly.
  3. Restore Data: If data corruption is suspected, restore from a known good backup if available.
  4. Retry Operation with Valid Inputs: Attempt to resume the node and verify that it participates in the cluster as expected.

Developer Notes

Developers should be aware of the potential impact of ERROR_CLUSTER_NODE_PAUSED on clustered applications and services. Proper error handling and logging are essential to ensure that applications can gracefully handle such conditions without causing system instability or data loss.

Related Errors

  • ERROR_CLUSTER_NOT_FOUND (5071, 0x13CF): Indicates the cluster was not found.
  • ERROR_CLUSTER_INVALID_NODE (5082, 0x1406): Indicates an invalid node ID is being used in a command or operation.

FAQ

Q: What does ERROR_CLUSTER_NODE_PAUSED mean?

A: It indicates that a cluster node has been paused and is no longer participating in the cluster management.

Q: How can I determine why a node was paused?

A: Review the event logs for the clusvc service and use tools like clusvc.msc or PowerShell cmdlets to check the state of the node.

Q: Can this error be caused by hardware issues?

A: Yes, hardware failures such as network interface or storage device problems can lead to a node being paused.

Summary

ERROR_CLUSTER_NODE_PAUSED is a specific error code indicating that a cluster node has been manually or automatically paused. This condition can impact the availability and reliability of clustered services. Proper diagnosis and resolution are crucial for maintaining the integrity and stability of the cluster environment.