| Previous | Next |
| PEER_E_CANNOT_CONVERT_PEER_NAME | PEER_E_NO_MORE |
PEER_E_INVALID_PEER_HOST_NAME
Diagnostic boundary for PEER_E_INVALID_PEER_HOST_NAME
HRESULT 0x80634002 marks the supplied DNS-compatible peer host name cannot be decoded into a valid PNRP peer name. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by peer-host-name to peer-name conversion and PNRP lookup, or reconstructed from cached text or another process?
- Preserve host string, label boundaries, escaping/case handling, source of the value and the output from the reverse conversion API.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
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.
Controlled comparison
Round-trip a known valid peer name through the official conversion functions and compare with the failing host string. 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 peer-name encoding; repeated network retries add no evidence. |
The call advances to PEER_E_CANNOT_CONVERT_PEER_NAME | PEER_E_CANNOT_CONVERT_PEER_NAME differs because the direction is reversed: this code rejects the encoded host name rather than failing to encode a peer name. |
| 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
Store the conversion output as an opaque protocol identifier and avoid generic DNS normalization that changes encoded labels. 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: 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.