| Previous | Next |
| PEER_E_CERT_STORE_CORRUPTED | PEER_E_CLOUD_NAME_AMBIGUOUS |
PEER_E_NO_CLOUD
The state transition represented by the HRESULT
PEER_E_NO_CLOUD — HRESULT 0x80631001 marks the requested PNRP cloud name or scope is not present in the local namespace-provider view. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PNRP Winsock namespace-provider cloud enumeration, registration and resolution that returned the HRESULT.
- Preserve requested cloud name, scope, interface and IPv6 addresses, cloud enumeration result, PNRP startup/service events and network profile.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: enumerate available clouds and repeat resolution with one returned exact cloud name rather than the configured alias.
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.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the cloud namespace described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original peer-name encoding was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_CLOUD_NAME_AMBIGUOUS differs because no-cloud finds zero matching clouds; ambiguous-cloud finds more than one cloud with the same scope/name interpretation. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Select an existing cloud or correct the interface/scope conditions that create it; DNS changes do not create a PNRP cloud. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- 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.