Cluster Node Paused (0x000013CE) — Three Fixes

1. Resume the Node (If Someone Paused It Manually)

Sounds stupid, but I've seen admins spend an hour chasing logs when the node was paused by accident. Someone ran a maintenance script that didn't resume it. Check the cluster manager or PowerShell.

Open Failover Cluster Manager, go to Nodes. If the status says Paused and the option Resume is available, that's your fix. Run this from an elevated PowerShell:

Get-ClusterNode | Where Status -eq 'Paused' | Resume-ClusterNode

If it resumes fine and stays up, you're done. If it pauses again within minutes, move to cause #2.

2. Disk Heartbeat Failure — The Real Culprit

In 80% of cases, 0x000013CE appears because a shared disk's heartbeat fails. The cluster sees the node can't talk to the witness or a quorum disk, so it pauses itself to prevent split-brain. This happens most often after a SAN hiccup or when you replaced a fiber channel card and forgot to update the multi-path settings.

First, check the system event log for event IDs 1135 or 1146. They'll point to the specific disk that's lost. Then run:

Get-ClusterResource | Where State -eq 'Failed'

You'll see a disk resource with status Failed. Right-click it and select Bring Online. If it comes up, run cluster validation right after:

Test-Cluster -Node NodeName

If the disk fails repeatedly, check the SAN zoning and multi-path I/O (MPIO) settings. Rescan the bus on the paused node:

diskpart
rescan

Then resume the node. If the disk keeps failing, it's hardware — call your SAN vendor.

3. Stuck Cluster Service or Corrupted State

Less common, but when it happens it's a headache. The cluster service itself gets hung on a pending action — like an interrupted drain or a failed CSV volume move. The node looks paused but won't resume normally.

Try forcing a resume with the -Force flag:

Resume-ClusterNode -Name NodeName -Force

If that doesn't work, restart the cluster service on the affected node:

Restart-Service ClusSvc

This drops the node, but when it comes back it should be unpaused. Only do this during maintenance windows — it will move all roles off the node temporarily.

If the node still shows paused after restart, check the cluster log for stuck resource states:

Get-ClusterLog -Node NodeName -TimeSpan 15

Look for entries like “Operation pending” or “Timeout reached”. If you find a resource stuck in OnlinePending or OfflinePending, manually fail it to another node, then bring it online again.

Quick-Reference Summary

Start with cause #1. If it's not that, go straight to #2. I've fixed dozens of these, and 9 out of 10 times it's disk heartbeat. The rest is a manual pause or a hung service. Don't overthink it.