What does Windows error code 4060 (PEERDIST_ERROR_ALREADY_COMPLETED) mean?

 
Previous Next
PEERDIST_ERROR_OPERATION_NOTFOUND PEERDIST_ERROR_OUT_OF_BOUNDS

PEERDIST_ERROR_ALREADY_COMPLETED

Can not perform the reqested operation because it has already been carried out.

PEERDIST_ERROR_ALREADY_COMPLETED is Win32 error 4060 (0xFDC) and belongs to Peer Distribution and BranchCache post-completion state handling. 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 Peer Distribution and BranchCache post-completion state handling rather than starting with a broad system repair.

Where the result appears

  • This result can surface during the post-completion state handling stage of a PeerDist publisher or consumer.
  • This result can surface during a BranchCache request where the caller attempted an action that is invalid after the PeerDist operation completed.
  • It can surface during an API call whose diagnosis depends on capture operation type, completion status, callback order, and repeated call.
  • It can surface during a recovery path that must consume the recorded completion once and reject duplicate finish, supply, or transition requests in the caller.

Likely causes

  • the caller attempted an action that is invalid after the PeerDist operation completed.
  • the caller made a stale assumption during post-completion state handling.
  • the observed PeerDist state no longer matched capture operation type, completion status, callback order, and repeated call.
  • the wrapper retried before it could consume the recorded completion once and reject duplicate finish, supply, or transition requests in the caller.

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 Peer Distribution and BranchCache post-completion state handling because a blind retry can hide stale state or repeat a non-idempotent change.

  • record capture operation type, completion status, callback order, and repeated call.
  • record the exact PeerDist function involved in post-completion state handling.
  • record the object generation used for post-completion state handling.
  • record PeerDistSvc status while evaluating the caller attempted an action that is invalid after the PeerDist operation completed.
  • record origin fallback behavior before attempting to consume the recorded completion once and reject duplicate finish, supply, or transition requests in the caller.

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

State boundary to prove

The decisive boundary for this Win32 error is whether the caller attempted an action that is invalid after the PeerDist operation completed. Prove or disprove that proposition using capture operation type, completion status, callback order, and repeated call together with the exact PeerDist function involved in post-completion state handling. When observations for this Win32 error disagree, preserve both and inspect the transition between them instead of choosing the more convenient value.

A focused validation for this Win32 error should recreate the relevant part of this situation: a completion callback and polling loop both finalize the same request. A single atomic completion owner prevents the second transition. The negative case should keep the responsible condition unchanged and confirm error 4060; the recovery case should change only that condition and verify a successful result without an unrecorded side effect.

Suggested diagnostic fields

For error 4060, keep winerr_4060_api, winerr_4060_object, winerr_4060_state_before, winerr_4060_request, winerr_4060_first_status, winerr_4060_verification. These fields distinguish the initial state, requested transition, first status, and verified recovery result.

Handling, retry, and recovery

consume the recorded completion once and reject duplicate finish, supply, or transition requests in the caller A retry is justified only after the recorded state that produced this specific code has changed.

Retry it only after evidence shows a change in Peer Distribution and BranchCache post-completion state handling. 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 4060, hexadecimal 0xFDC, and the producing API.
  • log the target object and observed Peer Distribution and BranchCache post-completion state handling 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

OPERATION_NOTFOUND often arises from late cancellation; ALREADY_COMPLETED confirms the target reached completion.

Practical example

A completion callback and polling loop both finalize the same request.

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 4060, 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.