| Previous | Next |
| PEER_E_NODE_NOT_FOUND | PEER_E_CONNECTION_NOT_AUTHENTICATED |
PEER_E_CONNECTION_FAILED
Which peer contract was rejected
PEER_E_CONNECTION_FAILED — HRESULT 0x80630109 marks a graph, group or direct connection attempt failed before a usable peer link was established. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphConnect, PeerGroupConnect, direct-connection calls and network tracing.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve target IPv6 endpoint, port, PNRP result, TCP connect outcome, firewall decision, graph/group events and any SSP or credential error that preceded the final code. |
| 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
Connect to one known reachable peer by explicit address and compare with name-based discovery to separate transport from resolution. 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_CONNECTION_REFUSED differs because refused identifies a reachable neighbor that is not accepting the connection; failed is the broader establishment failure. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Repair the first failing layer—resolution, route, listener, firewall or authentication—instead of retrying the aggregate connection call blindly. 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 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.