| 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 means that the human-readable friendly-name field supplied to a peer identity or group property is not accepted. The relevant API boundary includes PeerIdentityCreate and PeerGroupCreate/SetProperties.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| 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.
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.
Recommended change
Sanitize and length-check display text separately from peer names, classifiers and identity keys.
Technical references
Looking for a different code? Search another status or error code.