| Previous | Next |
| PEER_E_INVALID_PEER_HOST_NAME | PEER_E_PNRP_DUPLICATE_PEER_NAME |
PEER_E_NO_MORE
Where the peer stack rejects the operation
PEER_E_NO_MORE — HRESULT 0x80634003 marks a PNRP endpoint enumeration has been exhausted and there are no additional endpoints to return. 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 WSALookupServiceBegin/Next/End with the PNRP namespace provider.
- Preserve lookup handle, peer name, cloud, endpoints already returned, result count and whether the application incorrectly treats normal exhaustion as transport failure.
- 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
Enumerate a name with a known number of registrations and verify that the code appears only after the last endpoint. 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 lookup handle, peer name, cloud, endpoints already returned, result count and whether the application incorrectly treats normal exhaustion as transport failure. |
| After correction | finish the enumeration normally and act on collected endpoints; retry resolution only when freshness requirements justify it. |
Neighboring result
PEER_E_NO_CLOUD differs because no-more is successful exhaustion of an existing lookup; no-cloud means the namespace scope cannot be accessed. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Finish the enumeration normally and act on collected endpoints; retry resolution only when freshness requirements justify it. 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.