| Previous | Next |
| PEER_E_CLASSIFIER_TOO_LONG | PEER_E_NO_KEY_ACCESS |
PEER_E_TOO_MANY_IDENTITIES
The state transition represented by the HRESULT
PEER_E_TOO_MANY_IDENTITIES — HRESULT 0x80630202 marks the local Identity Manager cannot create another peer identity because its supported identity inventory is exhausted. 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 PeerEnumIdentities, PeerIdentityCreate and PeerIdentityDelete that returned the HRESULT.
- Preserve enumerated identities, owning applications, creation dates, temporary-identity cleanup policy and the identity-create request.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: enumerate and remove a disposable unused identity, then repeat the same creation request without changing its classifier.
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_GROUPS_EXIST differs because identity-count exhaustion is a capacity condition; groups-exist blocks deletion of one identity because group state still depends on it. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Reuse durable identities where appropriate and delete temporary identities when the application no longer needs them. 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.