| Previous | Next |
| PEER_E_INVALID_FRIENDLY_NAME | PEER_E_INVALID_CLASSIFIER_PROPERTY |
PEER_E_INVALID_ROLE_PROPERTY
Which peer contract was rejected
PEER_E_INVALID_ROLE_PROPERTY — HRESULT 0x80632071 marks a role identifier in group properties, invitation or credential issuance is not valid for the requested group operation. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGroupCreateInvitation, PeerGroupIssueCredentials and PEER_CREDENTIAL_INFO.
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 role GUID array, count, issuer member role, group version and the exact invitation/credential call. |
| 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
Issue a disposable invitation using a documented member role, then add or replace the failing role value. 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_NOT_AUTHORIZED differs because invalid-role rejects the role data itself; not-authorized rejects a valid operation attempted by a member without authority. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Use roles defined for the group and ensure the issuer is authorized to grant them. 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.