| Previous | Next |
| PEER_E_SERVICE_NOT_AVAILABLE | PEER_E_INVALID_PEER_HOST_NAME |
PEER_E_CANNOT_CONVERT_PEER_NAME
Where the peer stack rejects the operation
PEER_E_CANNOT_CONVERT_PEER_NAME — HRESULT 0x80634001 marks conversion from a peer name to the DNS-compatible PNRP host-name representation failed. Treat it as a cloud namespace result rather than a generic peer-networking failure.
PNRP is a Winsock namespace provider that resolves peer names to endpoint information inside an IPv6-based cloud. Cloud selection, registration and endpoint enumeration are distinct steps.
Evidence to preserve before retrying
- Record the first failing surface among peer-name/peer-host-name conversion functions in p2p.h.
- Preserve original peer name, secured/unsecured form, classifier, Unicode normalization, output-buffer handling and conversion API result.
- Place successful creation or discovery, state-changing events and the failing call on one timeline.
- Keep peer names, identities, record identifiers, invitation data and endpoints in their original Unicode or binary representation.
Controlled isolation
Convert a peer name returned by Identity Manager and compare with the manually supplied value. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Checkpoint | Question for this HRESULT |
|---|---|
| Before the API | Was the required peer-name encoding obtained in this process and user context? |
| At the HRESULT | Preserve original peer name, secured/unsecured form, classifier, Unicode normalization, output-buffer handling and conversion API result. |
| After correction | use API-generated peer names and preserve the exact encoded host form; do not pass a display name or ordinary DNS label as a peer name. |
Neighboring result
PEER_E_INVALID_PEER_HOST_NAME differs because cannot-convert starts with a peer name; invalid-peer-host-name starts with the DNS-compatible encoded representation. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Use API-generated peer names and preserve the exact encoded host form; do not pass a display name or ordinary DNS label as a peer name. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- Microsoft: About PNRP — it uses this source for the documented peer boundary.
- Microsoft Open Specifications: PNRP Version 4.0
- Microsoft: Peer names
- Microsoft: Registering a peer name
Looking for a different code? Search another status or error code.