| Previous | Next |
| PEER_E_NO_KEY_ACCESS | PEER_E_RECORD_NOT_FOUND |
PEER_E_GROUPS_EXIST
The state transition represented by the HRESULT
PEER_E_GROUPS_EXIST — HRESULT 0x80630204 marks identity deletion was requested while one or more local peer groups still depend on that identity. 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, group enumeration and PeerGroupDelete that returned the HRESULT.
- Preserve identity peer name, group enumeration, open group handles, exported configurations and the deletion call owner.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: use a disposable identity, create or join a group, attempt deletion, then delete/leave the dependent group and repeat.
Peer identities are secure peer names backed by user-scoped certificate and private-key material. The same identity may be referenced by PNRP registrations and by one or more secure peer groups.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the identity certificate 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 private-key ownership was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_IDENTITY_DELETED differs because groups-exist prevents deletion; identity-deleted means a later operation is still trying to use an identity that has already been removed. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Close and deliberately remove or migrate dependent groups before deleting the identity, preserving exports when the private key is still needed elsewhere. 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: About the Peer Identity Manager API — it uses this source for the documented peer boundary.
- Microsoft: Creating a peer identity
- Microsoft: Identity and group configuration import and export
- Microsoft: Common Peer Infrastructure return codes
Looking for a different code? Search another status or error code.