| Previous | Next |
| PEER_E_GRAPH_NOT_READY | PEER_E_GRAPH_IN_USE |
PEER_E_GRAPH_SHUTTING_DOWN
Which peer contract was rejected
PEER_E_GRAPH_SHUTTING_DOWN — HRESULT 0x80630014 marks graph teardown has started and the infrastructure no longer accepts new graph operations. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphClose, callback dispatch and application shutdown coordination.
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 shutdown initiator, outstanding callbacks, worker threads, open enumerations, direct connections and timestamps for close versus the rejected call. |
| 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
Block new work before initiating close, drain callbacks, and compare with a test that intentionally races one operation against graph teardown. 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_INVALID_GRAPH differs because after teardown completes the handle may become invalid; this code specifically identifies the in-progress shutdown interval. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Serialize shutdown with application work queues and release graph-dependent objects before invalidating the graph handle. 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.