| Previous | Next |
| PEER_E_DBINITIALIZATION_FAILED | PEER_E_DATABASE_ALREADY_PRESENT |
PEER_E_MAX_RECORD_SIZE_EXCEEDED
Diagnostic boundary for PEER_E_MAX_RECORD_SIZE_EXCEEDED
HRESULT 0x80630304 marks the serialized peer record exceeds the maximum size accepted by the graph or group record store. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGraphAddRecord, PeerGroupAddRecord and PEER_RECORD serialization, or reconstructed from cached text or another process?
- Preserve payload byte length, attribute XML length, signature/credential overhead, record type and size before and after serialization.
- 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
Submit a minimal record of the same type and add payload in measured increments while keeping attributes and expiration stable. 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_INVALID_RECORD_SIZE | PEER_E_INVALID_RECORD_SIZE differs because maximum-size-exceeded is a supported-format record that is too large; invalid-record-size indicates an inconsistent or illegal size field. |
| 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
Split application data into bounded records or store large content elsewhere and replicate only identifiers, hashes and compact metadata. 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.