| Previous | Next |
| PEER_E_INVALID_DATABASE | PEER_E_CONNECTION_NOT_FOUND |
PEER_E_TOO_MANY_ATTRIBUTES
Which peer contract was rejected
PEER_E_TOO_MANY_ATTRIBUTES — HRESULT 0x80630017 means that a peer record contains more application-defined attributes than the Peer Infrastructure accepts. The relevant API boundary includes PeerGraphAddRecord, PeerGroupAddRecord and PEER_RECORD.pszAttributes.
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 |
|---|---|
| Raw input | Preserve record type GUID, serialized attribute XML, attribute count, duplicate names, reserved names and the API call that adds or updates the record. |
Focused reproduction
Submit the same record while removing attributes one by one, keeping payload and expiration unchanged, until the boundary is isolated.
Why the comparison code is different
PEER_E_INVALID_ATTRIBUTES differs because too-many-attributes concerns quantity; invalid-attributes concerns XML/schema or name/type formatting.
Recommended change
Store only searchable fields as record attributes and move non-indexed metadata into the record payload.
Technical references
Looking for a different code? Search another status or error code.