| Previous | Next |
| PEER_E_DATABASE_ALREADY_PRESENT | PEER_E_IDENTITY_NOT_FOUND |
PEER_E_DATABASE_NOT_PRESENT
The state transition represented by the HRESULT
PEER_E_DATABASE_NOT_PRESENT — HRESULT 0x80630306 marks the graph or group operation expects a local database that is not present at the configured path. 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 PeerGraphOpen, PeerGroupOpen and database import/configuration paths that returned the HRESULT.
- Preserve resolved database path, user profile, graph/group identity, prior delete/export actions, filesystem events and configuration changes.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: log the fully normalized path and compare opening the missing target with creating a new disposable database under the same account.
Peer records combine a typed record structure, optional searchable XML attributes, payload data, creator metadata and expiration. The local database may receive records in an order different from application dependencies.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the record contract 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 local replicated store was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_RECORD_NOT_FOUND differs because a missing record does not imply that the database file itself is absent. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Restore/import the correct database or intentionally recreate the graph/group; do not create an empty store when historical membership or records are required. 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: Record attribute schema — it uses this source for the documented peer boundary.
- Microsoft: Record search query format
- Microsoft: Record dependencies
- Microsoft: Grouping API functions
Looking for a different code? Search another status or error code.