| Previous | Next |
| PEER_E_NO_CLOUD | PEER_E_INVALID_RECORD |
PEER_E_CLOUD_NAME_AMBIGUOUS
Which peer contract was rejected
PEER_E_CLOUD_NAME_AMBIGUOUS — HRESULT 0x80631005 marks the supplied PNRP cloud reference matches more than one cloud of the same scope and therefore does not select a unique namespace. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PNRP cloud enumeration, PeerGroupJoin optional cloud name and PNRP resolution calls.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve all enumerated cloud names and scopes, interface identifiers, the caller-supplied cloud string and the invitation/configuration value from which it came. |
| 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
Repeat the operation with the fully qualified cloud name returned by enumeration and compare with the ambiguous shorthand. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_NO_CLOUD differs because ambiguous means multiple candidates exist; no-cloud means none exist. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Persist and pass the exact cloud identifier rather than only a scope label. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical 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.