| Previous | Next |
| PEER_E_INVALID_ATTRIBUTES | PEER_E_CHAIN_TOO_LONG |
PEER_E_INVITATION_NOT_TRUSTED
Which peer contract was rejected
PEER_E_INVITATION_NOT_TRUSTED — HRESULT 0x80630701 marks the invitation supplied to join a secure peer group cannot be accepted as a valid trusted group credential package. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGroupCreateInvitation, PeerGroupParseInvitation and PeerGroupJoin.
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve invitation XML bytes, issuer identity, group peer name, GMC chain, signature verification result, expiry and out-of-band delivery provenance. |
| 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
Parse the invitation before joining and compare it with a newly issued invitation delivered without text re-encoding or truncation. 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_INVALID_CREDENTIAL differs because invalid-credential identifies an invalid join invitation structure/content; invitation-not-trusted emphasizes failed trust validation. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Obtain a fresh invitation from an authorized group administrator and preserve it as opaque data; do not edit certificate or base64 fields. 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: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.