| Previous | Next |
| PEER_E_GRAPH_SHUTTING_DOWN | PEER_E_INVALID_DATABASE |
PEER_E_GRAPH_IN_USE
Diagnostic boundary for PEER_E_GRAPH_IN_USE
HRESULT 0x80630015 marks a graph database import was requested while the graph remained connected or listening. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGraphImportDatabase, PeerGraphClose and listener/connection teardown, or reconstructed from cached text or another process?
- Preserve graph status, listening state, active connections, HGRAPH owners, import filename and proof that all graph handles were closed before import.
- 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
Disconnect and close the graph, import the same database, then reopen it; compare with an import attempted while listening. 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_GROUP_IN_USE | PEER_E_GROUP_IN_USE differs because the group variant applies to group database import or joining an already-open group, not a raw graph database. |
| 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
Make database import an offline maintenance operation and prevent other process components from reopening the graph during the maintenance window. 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.