| Previous | Next |
| PEER_E_INVALID_SEARCH | PEER_E_INVITATION_NOT_TRUSTED |
PEER_E_INVALID_ATTRIBUTES
Diagnostic boundary for PEER_E_INVALID_ATTRIBUTES
HRESULT 0x80630602 marks the attribute XML attached to a record violates the required attribute schema or naming/type rules. 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.pszAttributes, PeerGraphAddRecord and PeerGroupAddRecord, or reconstructed from cached text or another process?
- Preserve raw pszAttributes XML, encoding, attribute names, declared int/date/string types, reserved names and XML validation output.
- 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
Add the record first without custom attributes, then add one schema-valid attribute and reintroduce the failing attribute. 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_TOO_MANY_ATTRIBUTES | PEER_E_TOO_MANY_ATTRIBUTES differs because invalid-attributes is about format; too-many-attributes is a count limit after otherwise valid parsing. |
| 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
Correct XML, use alphanumeric attribute names, match declared types to values and reserve search attributes for fields that need indexing. 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.