| Previous | Next |
| PEER_E_INVALID_CREDENTIAL | PEER_E_UNSUPPORTED_VERSION |
PEER_E_INVALID_RECORD_SIZE
Diagnostic boundary for PEER_E_INVALID_RECORD_SIZE
HRESULT 0x80632083 marks the record structure reports a payload or field size that is inconsistent with the supplied buffers or record format. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PEER_RECORD data fields and record add/update APIs, or reconstructed from cached text or another process?
- Preserve declared and actual payload length, pointer validity, serialized byte count, attributes size, record flags and architecture bitness.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
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.
Controlled comparison
Construct the same record from a zero-initialized structure with measured byte lengths and compare with the original serializer output. Keep identity, graph or group ID, cloud and user context fixed unless one of them is the tested variable.
Decision table
| Observed result | Next action for this HRESULT |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and local replicated store; repeated network retries add no evidence. |
The call advances to PEER_E_MAX_RECORD_SIZE_EXCEEDED | PEER_E_MAX_RECORD_SIZE_EXCEEDED differs because invalid-size is inconsistent metadata; maximum-exceeded is a correctly measured record that is too large. |
| The controlled run succeeds but production does not | Compare user token, database path, cloud, endpoint, certificate chain and effective firewall policy. |
Safe remediation and verification
Calculate lengths from encoded bytes, not character counts, and keep buffer ownership valid through the API call. Back up exportable identity and group configuration, and hash database or invitation artifacts before modifying them.
The repair is complete only when the intended operation succeeds and its resulting connection, record, membership, endpoint or collaboration scope can be independently enumerated.
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.