| Previous | Next |
| PEER_E_NO_MORE | PEER_E_CONTACT_NOT_FOUND |
PEER_E_PNRP_DUPLICATE_PEER_NAME
Where the peer stack rejects the operation
PEER_E_PNRP_DUPLICATE_PEER_NAME — HRESULT 0x80634005 marks the same peer name is being registered more than once in the same PNRP cloud. 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 PNRP WSASetService registration and unregistration.
- Preserve peer name, cloud, endpoint/address, registration owner, service-instance identifier and existing namespace registrations.
- 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
Unregister the known local instance and register once, then compare with a deliberate second registration in the same cloud. 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 peer name, cloud, endpoint/address, registration owner, service-instance identifier and existing namespace registrations. |
| After correction | assign one owner per registration or use distinct service identities/endpoints according to the application design. |
Neighboring result
PEER_E_CONNECT_SELF differs because duplicate registration is namespace state; connect-self is endpoint selection resolving back to the local node. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Assign one owner per registration or use distinct service identities/endpoints according to the application design. 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.