| Previous | Next |
| PEER_E_PNRP_DUPLICATE_PEER_NAME | PEER_E_INVITE_CANCELLED |
PEER_E_CONTACT_NOT_FOUND
Where the peer stack rejects the operation
PEER_E_CONTACT_NOT_FOUND — HRESULT 0x80636001 marks the requested trusted contact is absent from the local Peer Collaboration contact store. Treat it as a presence session result rather than a generic peer-networking failure.
Peer Collaboration provides serverless presence, contacts, endpoint subscriptions and invitations. Its operations depend on an interactive user context, explicit sign-in scopes and firewall/privacy consent.
Evidence to preserve before retrying
- Record the first failing surface among PeerCollabEnumContacts, PeerCollabGetContact and invitation functions.
- Preserve contact peer name, contact enumeration, owning user profile, update/delete events and whether the application holds an obsolete PEER_CONTACT copy.
- 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
Enumerate contacts immediately before the operation and use one returned contact object, then compare with the stale identifier. 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 invitation workflow obtained in this process and user context? |
| At the HRESULT | Preserve contact peer name, contact enumeration, owning user profile, update/delete events and whether the application holds an obsolete PEER_CONTACT copy. |
| After correction | refresh the contact store view or re-establish trust through the intended user flow; do not silently invite a different discovered peer. |
Neighboring result
PEER_E_IDENTITY_NOT_FOUND differs because contact-not-found concerns another person in the collaboration contact store; identity-not-found concerns the local peer identity. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Refresh the contact store view or re-establish trust through the intended user flow; do not silently invite a different discovered peer. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- Microsoft: About the Peer Collaboration API — it uses this source for the documented peer boundary.
- Microsoft: Collaboration API functions
- Microsoft: People Near Me requirements
- Microsoft: Windows Firewall rules
Looking for a different code? Search another status or error code.