| Previous | Next |
| PEER_E_INVALID_RECORD | PEER_E_PASSWORD_DOES_NOT_MEET_POLICY |
PEER_E_NOT_AUTHORIZED
Which peer contract was rejected
PEER_E_NOT_AUTHORIZED — HRESULT 0x80632020 marks the authenticated group member lacks the role or record ownership authority required for the requested operation. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGroupSetProperties, record delete/update and PeerGroupIssueCredentials.
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 member identity, GMC roles, record creator, requested action, group properties and the credential chain used for the connection. |
| 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
Perform the operation as the record creator or a member with the documented administrator role and compare with the failing member. 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_CONNECTION_NOT_AUTHENTICATED differs because not-authorized occurs after an identity is recognized; not-authenticated means secure connection establishment failed. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Issue appropriate credentials or redesign the operation around allowed ownership rules; do not weaken invitation trust checks. 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.