What does Windows error code 5011 (ERROR_OBJECT_IN_LIST) mean?

 
Previous Next
ERROR_OBJECT_ALREADY_EXISTS ERROR_GROUP_NOT_AVAILABLE

ERROR_OBJECT_IN_LIST

The object is already in the list.

ERROR_OBJECT_IN_LIST is Win32 error 5011 (0x1393) and belongs to Failover clustering cluster list membership. For ERROR_OBJECT_IN_LIST, the system description identifies the immediate condition but does not identify the caller, object, policy, device, service instance, or transition that produced it.

Interpret ERROR_OBJECT_IN_LIST at the API boundary that returned it. Capture ERROR_OBJECT_IN_LIST before logging, cleanup, or another Windows call can replace the thread-local last-error value. For ERROR_OBJECT_IN_LIST, compare the recorded inputs with the documented precondition for Failover clustering cluster list membership rather than starting with a broad system repair.

Where this result appears

  • ERROR_OBJECT_IN_LIST can surface during Failover Cluster management during cluster list membership.
  • ERROR_OBJECT_IN_LIST can surface during Cluster service processing where the object is already present in the target cluster list or collection.
  • ERROR_OBJECT_IN_LIST can surface during a role or node transition whose evidence includes object identity and target list.
  • ERROR_OBJECT_IN_LIST can surface during automation expected to treat equivalent membership as success or remove it through the documented transition before re-adding.

Likely causes

  • For ERROR_OBJECT_IN_LIST, the object is already present in the target cluster list or collection.
  • For ERROR_OBJECT_IN_LIST, the management view for cluster list membership changed before the request committed.
  • For ERROR_OBJECT_IN_LIST, a concurrent cluster transition invalidated first insertion event.
  • For ERROR_OBJECT_IN_LIST, the caller attempted recovery without first confirming that it could treat equivalent membership as success or remove it through the documented transition before re-adding.

Diagnostic sequence

Diagnosis of ERROR_OBJECT_IN_LIST starts with the exact request type: read, write, create, transition, validation, cancellation, or administrative action. For ERROR_OBJECT_IN_LIST, identify the object generation and subsystem owner, then decide whether the failure happened before side effects, during a partial transition, or after completion. For ERROR_OBJECT_IN_LIST, this ordering matters in Failover clustering cluster list membership because a blind retry can hide stale state or repeat a non-idempotent change.

  • For ERROR_OBJECT_IN_LIST, record object identity and target list.
  • For ERROR_OBJECT_IN_LIST, record first insertion event.
  • For ERROR_OBJECT_IN_LIST, record concurrent caller and transaction.
  • For ERROR_OBJECT_IN_LIST, record list generation or configuration version.
  • For ERROR_OBJECT_IN_LIST, record UTC timestamp, cluster functional level, and the cluster list membership transition generation.

Correlate ERROR_OBJECT_IN_LIST with the owning component’s operational log, the Windows System log, and any subsystem trace. Telemetry for ERROR_OBJECT_IN_LIST 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 5011, hexadecimal 0x1393, and the producing API even when a localized message is also shown.

State boundary to prove

The decisive boundary for ERROR_OBJECT_IN_LIST is whether the object is already present in the target cluster list or collection. Prove or disprove that proposition using object identity and target list together with first insertion event. When observations for ERROR_OBJECT_IN_LIST disagree, preserve both and inspect the transition between them instead of choosing the more convenient value.

A focused validation for ERROR_OBJECT_IN_LIST should recreate the relevant part of this situation: two policy paths both add the same dependency entry. A uniqueness check prevents the duplicate insertion. The negative case should keep the responsible condition unchanged and confirm error 5011; the recovery case should change only that condition and verify a successful result without an unrecorded side effect.

Suggested diagnostic fields

For error 5011, keep winerr_5011_api, winerr_5011_object, winerr_5011_state_before, winerr_5011_request, winerr_5011_first_status, winerr_5011_verification. These fields distinguish the initial state, requested transition, first status, and verified recovery result.

Handling, retry, and recovery

Treat equivalent membership as success or remove it through the documented transition before re-adding. For ERROR_OBJECT_IN_LIST, generate a focused cluster log for the failure window and preserve the first error rather than only the final management message.

Retry ERROR_OBJECT_IN_LIST only after evidence shows a change in Failover clustering cluster list membership. For ERROR_OBJECT_IN_LIST, 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 ERROR_OBJECT_IN_LIST, query completion state explicitly.

What to log for support and telemetry

  • For ERROR_OBJECT_IN_LIST, log decimal 5011, hexadecimal 0x1393, and the producing API.
  • For ERROR_OBJECT_IN_LIST, log the target object and observed Failover clustering cluster list membership state.
  • For ERROR_OBJECT_IN_LIST, log caller identity, process and thread IDs, machine or node identity, and UTC time.
  • For ERROR_OBJECT_IN_LIST, log attempt number, elapsed time, previous result, and any partial side effect.
  • For ERROR_OBJECT_IN_LIST, retain the first lower-level or component-specific error before Win32 translation.

Difference from nearby codes

For ERROR_OBJECT_IN_LIST, eRROR_OBJECT_IN_LIST names the cluster-specific boundary for cluster list membership; a generic Win32 paraphrase would lose the object and transition context.

Practical example

Two policy paths both add the same dependency entry. A uniqueness check prevents the duplicate insertion.

Developer and administrator guidance

Code that handles ERROR_OBJECT_IN_LIST should keep its Win32 domain visible across exceptions, RPC responses, and JSON or REST wrappers. For ERROR_OBJECT_IN_LIST, administrators should verify the subsystem evidence before changing policy, deleting state, forcing failover, or replacing storage. Recovery is demonstrated only when a test observes 5011, changes the responsible condition, and confirms that the same operation succeeds without hidden data loss.

References

Looking for a different code? Search another status or error code.