| Previous | Next |
| PEER_E_GROUPS_EXIST | PEER_E_DATABASE_ACCESSDENIED |
PEER_E_RECORD_NOT_FOUND
Which peer contract was rejected
PEER_E_RECORD_NOT_FOUND — HRESULT 0x80630301 marks the requested record ID is absent from the local graph or group record database at the time of lookup or update. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphGetRecord, PeerGroupGetRecord, update/delete calls and record event handling.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve record GUID, record type, creator ID, local database generation, expiration, delete events and whether synchronization has completed. |
| 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
Enumerate records of the expected type and immediately retrieve one returned ID, then compare with the stale requested ID. 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_DATABASE_NOT_PRESENT differs because record-not-found concerns one logical record inside an available database; database-not-present means the store itself is missing. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Refresh application indexes after record deletion/expiration and tolerate replication order rather than assuming a remote record is already local. 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: 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.