| Previous | Next |
| PEER_E_RECORD_NOT_FOUND | PEER_E_DBINITIALIZATION_FAILED |
PEER_E_DATABASE_ACCESSDENIED
Which peer contract was rejected
PEER_E_DATABASE_ACCESSDENIED — HRESULT 0x80630302 marks the process lacks file-system or security access required to open or modify the local peer graph/group database. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphOpen, PeerGroupOpen and database import/export file access.
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 database path, file owner and ACL, process token, profile redirection, antivirus/backup locks and the requested open/import operation. |
| 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
Open the same database under the owning user with normal integrity and compare with a copied database whose ACLs are intentionally restricted. 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_NO_KEY_ACCESS differs because database access protects replicated records; key access protects identity private-key material, often under different ACLs. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Restore least-privilege access for the intended user and stop using administrator copies that change ownership or profile location. 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.