| Previous | Next |
| PEER_E_INVALID_GRAPH | PEER_E_DUPLICATE_GRAPH |
PEER_E_DBNAME_CHANGED
Diagnostic boundary for PEER_E_DBNAME_CHANGED
HRESULT 0x80630011 marks the same graph was opened in one process with a database name different from the name used by its first 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 PeerGraphOpen and the application code that derives the graph database name, or reconstructed from cached text or another process?
- Preserve graph ID, peer ID, both database names and normalized paths, open-call order, process lifetime and configuration source for each name.
- 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
Open the graph twice in one test process using the original database name, then change only the second name to reproduce the mismatch. 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_DUPLICATE_GRAPH | PEER_E_DUPLICATE_GRAPH differs because duplicate-graph is about reusing a graph ID for creation; database-name-changed is an inconsistent open configuration. |
| 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
Choose one stable database name per graph within the process and migrate or import data only while the graph is closed. 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.