| Previous | Next |
| ERROR_CLUSTERLOG_EXCEEDS_MAXSIZE | ERROR_CLUSTERLOG_NOT_ENOUGH_SPACE |
ERROR_CLUSTERLOG_CHKPOINT_NOT_FOUND
ERROR_CLUSTERLOG_CHKPOINT_NOT_FOUND means the cluster log did not contain the checkpoint record expected by the operation. This can follow an interrupted update or an inconsistent persistent log.
What to check
- Collect cluster logs from all nodes and compare the event sequence around the failed operation.
- Check whether a node restart, power loss, disk error, or cluster service interruption occurred during a configuration change.
- Run validation after the cluster is stable; do not make unrelated configuration changes while membership is changing.
Get-ClusterLog -UseLocalTime -Destination C:\Temp
Microsoft: Validate hardware for a failover cluster
Microsoft: Troubleshoot unexpected cluster failover
Looking for a different code? Search another status or error code.