| Previous | Next |
| PEER_E_CONNECTION_NOT_FOUND | PEER_E_ALREADY_LISTENING |
PEER_E_CONNECT_SELF
Where the peer stack rejects the operation
PEER_E_CONNECT_SELF — HRESULT 0x80630106 marks a direct-connection request resolved to the local node instead of a distinct peer. 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 PeerGraphOpenDirectConnection or PeerGroupOpenDirectConnection and node enumeration.
- Preserve local node ID and addresses, target node ID, resolved endpoint list, graph/group identity and the selection algorithm that chose the endpoint.
- 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
Filter the local node from an enumeration and compare a connection attempt to a known remote node with one to the local entry. 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 local node ID and addresses, target node ID, resolved endpoint list, graph/group identity and the selection algorithm that chose the endpoint. |
| After correction | reject self endpoints before opening the direct connection and keep node identity separate from display or friendly names. |
Neighboring result
PEER_E_PNRP_DUPLICATE_PEER_NAME differs because duplicate publication can yield multiple endpoints for one name, but connecting to the local endpoint is the immediate self-connection defect. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Reject self endpoints before opening the direct connection and keep node identity separate from display or friendly names. 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.