| Previous | Next |
| PEER_E_DUPLICATE_GRAPH | PEER_E_GRAPH_SHUTTING_DOWN |
PEER_E_GRAPH_NOT_READY
Which peer contract was rejected
PEER_E_GRAPH_NOT_READY — HRESULT 0x80630013 marks the requested operation requires a connected graph, but the local node has not reached connected state. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphConnect, PeerGraphGetStatus, graph event registration and the failed graph operation.
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 PeerGraphGetStatus result, connect and listen events, neighbor count, PNRP resolution outcome, callback sequence and the operation attempted too early. |
| 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
Wait for the graph status/event that proves connectivity before the operation, and compare with the same call immediately after open. 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_GRAPH_SHUTTING_DOWN differs because not-ready is a pre-connect or disconnected state; shutting-down is a terminal transition after teardown has begun. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Gate connectivity-dependent work on graph status and events rather than on successful open alone. 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.