| Previous | Next |
| PEER_E_TOO_MANY_IDENTITIES | PEER_E_GROUPS_EXIST |
PEER_E_NO_KEY_ACCESS
Where the peer stack rejects the operation
PEER_E_NO_KEY_ACCESS — HRESULT 0x80630203 marks the current security context cannot access the directory or protected material that stores a peer identity private key. Treat it as a identity certificate result rather than a generic peer-networking failure.
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.
Evidence to preserve before retrying
- Record the first failing surface among PeerIdentityGetXML, PeerIdentityExport/Import and identity-backed group operations.
- Preserve user SID, integrity/elevation context, profile path, key-container permissions, roaming/profile state and the API that first needed the key.
- Place successful creation or discovery, state-changing events and the failing call on one timeline.
- Keep peer names, identities, record identifiers, invitation data and endpoints in their original Unicode or binary representation.
Controlled isolation
Run the operation as the same non-elevated user who created the identity and compare with a different account or damaged profile copy. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Checkpoint | Question for this HRESULT |
|---|---|
| Before the API | Was the required private-key ownership obtained in this process and user context? |
| At the HRESULT | Preserve user SID, integrity/elevation context, profile path, key-container permissions, roaming/profile state and the API that first needed the key. |
| After correction | restore access to the original user key material or import a valid encrypted identity export; do not replace certificates without preserving group membership implications. |
Neighboring result
PEER_E_CERT_STORE_CORRUPTED differs because no-key-access is an authorization or availability problem; cert-store-corrupted means the stored certificate data cannot be trusted or parsed. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Restore access to the original user key material or import a valid encrypted identity export; do not replace certificates without preserving group membership implications. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- 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.