What does HRESULT 0x80630103 (PEER_E_CONNECTION_NOT_FOUND) mean?

PEER_E_CONNECTION_NOT_FOUND

Where the peer stack rejects the operation

PEER_E_CONNECTION_NOT_FOUND — HRESULT 0x80630103 marks the requested direct or neighbor connection identifier is no longer present in the graph or group connection table. Treat it as a graph lifecycle result rather than a generic peer-networking failure.

Evidence to preserve before retrying

• Record the first failing surface among PeerGraphEnumConnections, PeerGraphCloseDirectConnection, PeerGroupEnumConnections and PeerGroupCloseDirectConnection.
• Preserve connection ID, node ID, connection type, enumeration snapshot, disconnect event order and whether another thread already closed the link.
• 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

Enumerate active connections immediately before closing or sending, then repeat after processing a disconnect event. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.

Neighboring result

PEER_E_NODE_NOT_FOUND differs because node-not-found refers to graph node identity; connection-not-found refers to a specific live link object. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.

Safe response

Treat connection IDs as ephemeral and remove them from application state as soon as the corresponding connection event arrives. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.

References

• Microsoft: About the Peer Graphing API.
• Microsoft Open Specifications: Peer-to-Peer Graphing Protocol
• Microsoft: Security Service Providers for Peer Graphing
• Microsoft: Common Peer Infrastructure return codes