| Previous | Next |
| PEER_E_INVITE_CANCELLED | PEER_E_NOT_SIGNED_IN |
PEER_E_INVITE_RESPONSE_NOT_AVAILABLE
Which peer contract was rejected
PEER_E_INVITE_RESPONSE_NOT_AVAILABLE — HRESULT 0x80637001 marks the caller requested an asynchronous invitation result before the completion event was signaled. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerCollabAsyncInviteContact/Endpoint and PeerCollabGetInvitationResponse.
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 async handle, event handle, wait result, callback order, timeout chosen by the application and invitation target. |
| 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
Wait for the documented completion event and retrieve the result once, comparing with an immediate premature retrieval. 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_TIMEOUT differs because response-not-available is premature polling; timeout is a completed wait/connect attempt that exceeded its allowed interval. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Use event-driven completion or a bounded wait and keep the invitation handle valid until the response is consumed. 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.