| Previous | Next |
| PEER_E_CLOUD_NAME_AMBIGUOUS | PEER_E_NOT_AUTHORIZED |
PEER_E_INVALID_RECORD
Which peer contract was rejected
PEER_E_INVALID_RECORD — HRESULT 0x80632010 marks the PEER_RECORD supplied to the grouping layer violates a required structural, identity or field invariant. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGroupAddRecord, PeerGroupUpdateRecord and PEER_RECORD.
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve record type and ID, creator/modifier IDs, payload pointer and length, attributes, expiration, flags and the add/update/delete API used. |
| 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
Construct a zero-extra-field record using the documented structure, then add each optional field until the rejected invariant is isolated. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
This result_SIZE differs because invalid-record is the broad structural verdict; invalid-record-size isolates a size-field inconsistency. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Repair the specific field rather than regenerating group credentials or deleting the database. 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: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.