| Previous | Next |
| PEER_E_INVALID_ROLE_PROPERTY | PEER_E_INVALID_RECORD_EXPIRATION |
PEER_E_INVALID_CLASSIFIER_PROPERTY
Diagnostic boundary for PEER_E_INVALID_CLASSIFIER_PROPERTY
HRESULT 0x80632072 marks the classifier embedded in the invitation used to join the group is invalid or inconsistent with the group identity. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGroupCreateInvitation, PeerGroupParseInvitation and PeerGroupJoin, or reconstructed from cached text or another process?
- Preserve invitation XML, classifier value, group peer name, issuer, signature result and output from PeerGroupParseInvitation.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
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.
Controlled comparison
Parse a freshly generated invitation from the same group and compare its classifier field without editing either XML document. Keep identity, graph or group ID, cloud and user context fixed unless one of them is the tested variable.
Decision table
| Observed result | Next action for this HRESULT |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and GMC trust chain; repeated network retries add no evidence. |
The call advances to PEER_E_INVALID_CLASSIFIER | PEER_E_INVALID_CLASSIFIER differs because invalid-classifier can arise during general identity/group creation; classifier-property pinpoints the join invitation field. |
| The controlled run succeeds but production does not | Compare user token, database path, cloud, endpoint, certificate chain and effective firewall policy. |
Safe remediation and verification
Replace the invitation with a newly issued opaque package from the correct group; manual classifier edits invalidate the credential context. Back up exportable identity and group configuration, and hash database or invitation artifacts before modifying them.
The repair is complete only when the intended operation succeeds and its resulting connection, record, membership, endpoint or collaboration scope can be independently enumerated.
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.