| Previous | Next |
| PEER_E_EVENT_HANDLE_NOT_FOUND | PEER_E_INVALID_ATTRIBUTES |
PEER_E_INVALID_SEARCH
Where the peer stack rejects the operation
PEER_E_INVALID_SEARCH — HRESULT 0x80630601 marks the XML record-search expression does not conform to the peersearch query grammar. Treat it as a record contract result rather than a generic peer-networking failure.
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.
Evidence to preserve before retrying
- Record the first failing surface among PeerGraphSearchRecords, PeerGroupSearchRecords and the Record Search Query Format.
- Preserve complete query XML, namespace URI, element nesting, comparison operator, escaping, attribute type and parser error location.
- Place successful creation or discovery, state-changing events and the failing call on one timeline.
- Keep peer names, identities, record identifiers, invitation data and endpoints in their original Unicode or binary representation.
Controlled isolation
Start with one documented clause against a reserved attribute, then add each logical operator or custom attribute separately. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Checkpoint | Question for this HRESULT |
|---|---|
| Before the API | Was the required local replicated store obtained in this process and user context? |
| At the HRESULT | Preserve complete query XML, namespace URI, element nesting, comparison operator, escaping, attribute type and parser error location. |
| After correction | generate queries from a schema-aware builder and validate XML before calling the search API. |
Neighboring result
PEER_E_INVALID_ATTRIBUTES differs because invalid-search rejects the query document; invalid-attributes rejects the attribute XML stored on a record. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Generate queries from a schema-aware builder and validate XML before calling the search API. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
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.