| Previous | Next |
| PEER_E_INVALID_CLASSIFIER | PEER_E_INVALID_ROLE_PROPERTY |
PEER_E_INVALID_FRIENDLY_NAME
Which peer contract was rejected
PEER_E_INVALID_FRIENDLY_NAME — HRESULT 0x80632070 marks the human-readable friendly-name field supplied to a peer identity or group property is not accepted. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerIdentityCreate and PeerGroupCreate/SetProperties.
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 raw Unicode value, length, embedded control characters, source encoding, structure field and create/set API. |
| 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
Substitute a short printable test label while leaving protocol IDs and credentials unchanged. 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_PEER_NAME differs because friendly name is presentation metadata; peer name is a protocol identity used by PNRP and security. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Sanitize and length-check display text separately from peer names, classifiers and identity keys. 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.