| Previous | Next |
| PEER_E_ALREADY_LISTENING | PEER_E_CONNECTION_FAILED |
PEER_E_NODE_NOT_FOUND
Where the peer stack rejects the operation
PEER_E_NODE_NOT_FOUND — HRESULT 0x80630108 marks a node-specific graph operation used a node ID that is absent from the current graph view. 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 PeerGraphEnumNodes, graph events and node-specific Graphing API calls.
- Preserve node ID, enumeration generation, node-change events, graph synchronization state and the operation that consumed the stale identifier.
- 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
Refresh the node enumeration immediately before the operation and compare the stale ID with a currently returned node ID. 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 node ID, enumeration generation, node-change events, graph synchronization state and the operation that consumed the stale identifier. |
| After correction | invalidate cached node IDs on node removal and after graph reopen or resynchronization. |
Neighboring result
PEER_E_CONNECTION_NOT_FOUND differs because a node may still exist without a particular connection, and a connection can disappear before the node record is removed. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Invalidate cached node IDs on node removal and after graph reopen or resynchronization. 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.