| 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 means that the PEER_RECORD supplied to the grouping layer violates a required structural, identity or field invariant. The relevant API boundary includes PeerGroupAddRecord, PeerGroupUpdateRecord and PEER_RECORD.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| 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.
Why the comparison code is different
PEER_E_INVALID_RECORD_SIZE isolates a size-field inconsistency, while PEER_E_INVALID_RECORD is the broader structural verdict.
Recommended change
Repair the specific field rather than regenerating group credentials or deleting the database.
Technical references
Looking for a different code? Search another status or error code.