| Previous | Next |
| PEER_E_DATABASE_NOT_PRESENT | PEER_E_EVENT_HANDLE_NOT_FOUND |
PEER_E_IDENTITY_NOT_FOUND
The state transition represented by the HRESULT
PEER_E_IDENTITY_NOT_FOUND — HRESULT 0x80630401 marks the local peer identity named by the operation is not present in the Identity Manager store. 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, PeerIdentityImport and identity-consuming Grouping/PNRP calls that returned the HRESULT.
- Preserve identity peer name, enumeration result, user profile and SID, import history, deletion events and the group/PNRP operation consuming the identity.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: enumerate identities under the same user and compare the requested name with an identity returned by the API.
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 not-found is discovered at lookup; identity-deleted often appears when a previously selected identity is removed during a longer operation. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Select an existing identity or import the encrypted identity package that owns the required private key; do not substitute a new identity for existing group 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: 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.