| Previous | Next |
| PEER_E_GRAPH_IN_USE | PEER_E_TOO_MANY_ATTRIBUTES |
PEER_E_INVALID_DATABASE
The state transition represented by the HRESULT
PEER_E_INVALID_DATABASE — HRESULT 0x80630016 marks the graph ID encoded by the imported database does not agree with the graph identity implied by the target database path or import context. 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 PeerGraphExportDatabase, PeerGraphImportDatabase and graph identity metadata that returned the HRESULT.
- Preserve source database hash, embedded graph ID if available, target graph ID, source and destination paths, export provenance and import-call parameters.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: export a database from the intended graph and import it into a fresh matching target; then compare with a database exported from a different graph.
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_DBINITIALIZATION_FAILED differs because initialization failure concerns loading or upgrading the database; invalid-database identifies a graph-identity mismatch. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Use the database only with its originating graph identity or perform a supported export/import workflow rather than renaming files to simulate another graph. 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.