| Previous | Next |
| PEER_E_CONNECTION_NOT_AUTHENTICATED | PEER_E_CLASSIFIER_TOO_LONG |
PEER_E_CONNECTION_REFUSED
Where the peer stack rejects the operation
PEER_E_CONNECTION_REFUSED — HRESULT 0x8063010B marks the selected neighbor was reachable but declined or could not accept the incoming mesh connection. Treat it as a graph lifecycle result rather than a generic peer-networking failure.
Peer Graphing maintains a connected set of nodes, replicates records and exposes separate graph, node, connection and event lifetimes. A graph database being open is not the same as the node being connected.
Evidence to preserve before retrying
- Record the first failing surface among PeerGraphConnect, PeerGroupConnect and remote listener diagnostics.
- Preserve remote endpoint, listener status, remote graph/group state, concurrent connection count, refusal timing and remote event logs.
- 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
Connect to the same endpoint after confirming its listener and group/graph state, then compare with another active member. 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 node or connection state obtained in this process and user context? |
| At the HRESULT | Preserve remote endpoint, listener status, remote graph/group state, concurrent connection count, refusal timing and remote event logs. |
| After correction | fix the remote listener, capacity or lifecycle state, or select another member; local database repair is unrelated to an explicit remote refusal. |
Neighboring result
PEER_E_NO_MEMBER_CONNECTIONS differs because no-member-connections is a group discovery outcome after members are found; refused is the response from a particular neighbor. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Fix the remote listener, capacity or lifecycle state, or select another member; local database repair is unrelated to an explicit remote refusal. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- Microsoft: About the Peer Graphing API — it uses this source for the documented peer boundary.
- Microsoft Open Specifications: Peer-to-Peer Graphing Protocol
- Microsoft: Security Service Providers for Peer Graphing
- Microsoft: Common Peer Infrastructure return codes
Looking for a different code? Search another status or error code.