| Previous | Next |
| PEER_E_CONTACT_NOT_FOUND | PEER_E_INVITE_RESPONSE_NOT_AVAILABLE |
PEER_E_INVITE_CANCELLED
Which peer contract was rejected
PEER_E_INVITE_CANCELLED — HRESULT 0x80637000 marks the application invitation operation was explicitly cancelled rather than failing in discovery, transport or trust validation. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerCollabAsyncInviteContact/Endpoint and invitation result/cancel functions.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve cancellation initiator, async invitation handle, UI action, target endpoint, callback/event order and whether cancellation raced completion. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Run one invitation to completion and one with a controlled user cancellation after dispatch. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_INVITE_RESPONSE_NOT_AVAILABLE differs because cancelled has a final cancellation decision; response-not-available means the asynchronous result is not ready yet. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Treat cancellation as a terminal user decision, release the async handle and avoid automatic resubmission. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical 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.