| Previous | Next |
| PEER_E_IDENTITY_NOT_FOUND | PEER_E_INVALID_SEARCH |
PEER_E_EVENT_HANDLE_NOT_FOUND
The state transition represented by the HRESULT
PEER_E_EVENT_HANDLE_NOT_FOUND — HRESULT 0x80630501 marks an event retrieval or unregister call used an event handle that is unknown, already unregistered or belongs to another graph/group object. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PeerGraphRegisterEvent/GetEventData/UnregisterEvent and corresponding PeerGroup functions that returned the HRESULT.
- Preserve event handle value, registration call and filters, owning graph/group handle, unregister order, callback thread and handle reuse.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: register a single event handle, retrieve one event, unregister it once, and compare with a deliberate second unregister or cross-object use.
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.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the graph lifecycle described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original node or connection state was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_INVALID_GRAPH differs because the event handle can be wrong even when the graph handle is valid; invalid-graph concerns the graph object itself. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Tie each event handle to its owner and invalidate it immediately after unregister or graph/group close. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- 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.