| Previous | Next |
| ERROR_CLUSTER_INTERNAL_INVALID_FUNCTION | ERROR_CLUSTER_PARTIAL_SEND |
ERROR_CLUSTER_PARAMETER_OUT_OF_BOUNDS
A parameter value is out of acceptable range.
ERROR_CLUSTER_PARAMETER_OUT_OF_BOUNDS is Win32 error 5913 (0x1719) and belongs to Failover clustering cluster parameter range validation. The system description identifies the immediate condition but does not identify the caller, object, policy, device, service instance, or transition that produced it.
Interpret this result at the API boundary that returned it. Capture it before logging, cleanup, or another Windows call can replace the thread-local last-error value. Compare the recorded inputs with the documented precondition for Failover clustering cluster parameter range validation rather than starting with a broad system repair.
Where the result appears
- This result can surface during Failover Cluster management during cluster parameter range validation.
- This result can surface during Cluster service processing where a supplied cluster parameter lies outside the accepted range.
- It can surface during a role or node transition whose evidence includes parameter name, type, and raw value.
- It can surface during automation expected to correct the value and validate units and integer width before resubmitting the operation.
Likely causes
- a supplied cluster parameter lies outside the accepted range.
- the management view for cluster parameter range validation changed before the request committed.
- a concurrent cluster transition invalidated API or PowerShell command.
- the caller attempted recovery without first confirming that it could correct the value and validate units and integer width before resubmitting the operation.
Diagnostic sequence
Diagnosis of it starts with the exact request type: read, write, create, transition, validation, cancellation, or administrative action. Identify the object generation and subsystem owner, then decide whether the failure happened before side effects, during a partial transition, or after completion. This ordering matters in Failover clustering cluster parameter range validation because a blind retry can hide stale state or repeat a non-idempotent change.
- record parameter name, type, and raw value.
- record API or PowerShell command.
- record documented range for the cluster version.
- record serialization and unit conversion before the request.
- record UTC timestamp, cluster functional level, and the cluster parameter range validation transition generation.
Correlate it with the owning component’s operational log, the Windows System log, and any subsystem trace. Telemetry for it should preserve native identifiers such as a path or file ID, handle generation, node or peer identity, policy ID, object version, offset and length, or transaction token. Retain decimal 5913, hexadecimal 0x1719, and the producing API even when a localized message is also shown.
State boundary to prove
The decisive boundary for it is whether a supplied cluster parameter lies outside the accepted range. Prove or disprove that proposition using parameter name, type, and raw value together with API or PowerShell command. When observations for it disagree, preserve both and inspect the transition between them instead of choosing the more convenient value.
A focused validation for it should recreate the relevant part of this situation: automation supplies milliseconds where seconds are expected, producing a value outside the cluster property range. The negative case should keep the responsible condition unchanged and confirm error 5913; the recovery case should change only that condition and verify a successful result without an unrecorded side effect.
Suggested diagnostic fields
For error 5913, keep winerr_5913_api, winerr_5913_object, winerr_5913_state_before, winerr_5913_request, winerr_5913_first_status, winerr_5913_verification. These fields distinguish the initial state, requested transition, first status, and verified recovery result.
Handling, retry, and recovery
Correct the value and validate units and integer width before resubmitting the operation. Generate a focused cluster log for the failure window and preserve the first error rather than only the final management message.
Retry it only after evidence shows a change in Failover clustering cluster parameter range validation. Initialization, asynchronous completion, recall, or service readiness can justify bounded backoff; malformed metadata, invalid identifiers, policy rejection, unsupported versions, and integrity failures require correction. Before repeating a write or configuration operation after it, query completion state explicitly.
What to log for support and telemetry
- log decimal 5913, hexadecimal
0x1719, and the producing API. - log the target object and observed Failover clustering cluster parameter range validation state.
- log caller identity, process and thread IDs, machine or node identity, and UTC time.
- log attempt number, elapsed time, previous result, and any partial side effect.
- retain the first lower-level or component-specific error before Win32 translation.
Difference from nearby codes
It names the cluster-specific boundary for cluster parameter range validation; a generic Win32 paraphrase would lose the object and transition context.
Practical example
Automation supplies milliseconds where seconds are expected, producing a value outside the cluster property range.
Developer and administrator guidance
Code that handles it should keep its Win32 domain visible across exceptions, RPC responses, and JSON or REST wrappers. Administrators should verify the subsystem evidence before changing policy, deleting state, forcing failover, or replacing storage. Recovery is demonstrated only when a test observes 5913, changes the responsible condition, and confirms that the same operation succeeds without hidden data loss.
References
- Microsoft: System Error Codes (4000–5999) — reference for error 5913.
- Microsoft: Failover clustering documentation — reference for error 5913.
- Microsoft: Get-ClusterLog — reference for error 5913.
- Microsoft: Troubleshoot unexpected cluster failover — reference for error 5913.
Looking for a different code? Search another status or error code.