| Previous | Next |
| PEER_E_INVALID_GROUP | PEER_E_NO_MEMBER_CONNECTIONS |
PEER_E_NO_MEMBERS_FOUND
Where the peer stack rejects the operation
PEER_E_NO_MEMBERS_FOUND — HRESULT 0x80632094 marks PNRP/group discovery completed without finding any active member that can bootstrap the connection. Treat it as a group membership result rather than a generic peer-networking failure.
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Evidence to preserve before retrying
- Record the first failing surface among PeerGroupConnect, PNRP resolution and group member publication.
- Preserve group peer name, cloud, scope, PNRP resolution results, local credential validity, remote publication state and timestamps.
- 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
Bring one known member online and publishing in the same cloud, then repeat the group connection without changing the invitation. 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 GMC trust chain obtained in this process and user context? |
| At the HRESULT | Preserve group peer name, cloud, scope, PNRP resolution results, local credential validity, remote publication state and timestamps. |
| After correction | restore at least one reachable publishing member or use a known address if the API workflow supports it. |
Neighboring result
PEER_E_NO_MEMBER_CONNECTIONS differs because no-members-found means discovery returned none; no-member-connections means candidates were found but could not accept a connection. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Restore at least one reachable publishing member or use a known address if the API workflow supports it. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
- Microsoft: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.