| Previous | Next |
| PEER_E_NOT_LICENSED | PEER_E_DBNAME_CHANGED |
PEER_E_INVALID_GRAPH
Diagnostic boundary for PEER_E_INVALID_GRAPH
HRESULT 0x80630010 marks the HGRAPH value supplied to a Graphing API is not a live handle returned by graph creation or open. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGraphCreate, PeerGraphOpen, PeerGraphClose and graph operations that consume HGRAPH, or reconstructed from cached text or another process?
- Preserve the handle value, creating call, graph ID, database path, owning thread, close/shutdown timestamp and the first API that rejected the handle.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
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.
Controlled comparison
Perform the same graph operation once with the fresh handle and once after PeerGraphClose, keeping every other argument identical. Keep identity, graph or group ID, cloud and user context fixed unless one of them is the tested variable.
Decision table
| Observed result | Next action for this HRESULT |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and node or connection state; repeated network retries add no evidence. |
The call advances to PEER_E_GRAPH_SHUTTING_DOWN | PEER_E_GRAPH_SHUTTING_DOWN differs because a valid handle can be rejected during shutdown, while invalid-graph means the handle itself is not accepted as a live graph object. |
| The controlled run succeeds but production does not | Compare user token, database path, cloud, endpoint, certificate chain and effective firewall policy. |
Safe remediation and verification
Fix handle ownership and lifetime; never cache HGRAPH values across graph close, process restart or database import. Back up exportable identity and group configuration, and hash database or invitation artifacts before modifying them.
The repair is complete only when the intended operation succeeds and its resulting connection, record, membership, endpoint or collaboration scope can be independently enumerated.
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.