| Previous | Next |
| PEER_E_INVALID_PEER_NAME | PEER_E_INVALID_FRIENDLY_NAME |
PEER_E_INVALID_CLASSIFIER
The state transition represented by the HRESULT
PEER_E_INVALID_CLASSIFIER — HRESULT 0x80632060 marks the classifier component used for an identity, group or peer name contains an unacceptable format or value. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PeerIdentityCreate, group properties and peer-name construction that returned the HRESULT.
- Preserve classifier string, length, encoding, surrounding peer-name form and whether the value came from properties or an invitation.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: replace only the classifier with a short known-valid alphanumeric value and regenerate the peer name through the API.
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.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the group membership described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original GMC trust chain was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_CLASSIFIER_TOO_LONG differs because invalid-classifier is content/syntax; classifier-too-long is specifically a length boundary. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Validate classifier syntax before identity/group creation and avoid treating a friendly display name as a classifier. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- 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.