| Previous | Next |
| PEER_E_UNABLE_TO_LISTEN | PEER_E_SERVICE_NOT_AVAILABLE |
PEER_E_IDENTITY_DELETED
The state transition represented by the HRESULT
PEER_E_IDENTITY_DELETED — HRESULT 0x806320A0 marks an operation retained an identity reference after that identity was deleted from the local Identity Manager. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PeerIdentityDelete and identity-backed Grouping operations that returned the HRESULT.
- Preserve identity peer name, deletion time, group handles using it, worker/callback lifetime and the operation that resumed after deletion.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: keep the identity present through the complete asynchronous operation, then reproduce deletion only after all group handles close.
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the group membership described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original GMC trust chain was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_IDENTITY_NOT_FOUND differs because identity-deleted highlights lifetime/race after prior use; identity-not-found is a direct lookup failure. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Serialize identity deletion with group and PNRP activity, and cancel dependent work before removing credentials. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- Microsoft: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.