| Previous | Next |
| PEER_E_NO_MEMBERS_FOUND | PEER_E_UNABLE_TO_LISTEN |
PEER_E_NO_MEMBER_CONNECTIONS
The state transition represented by the HRESULT
PEER_E_NO_MEMBER_CONNECTIONS — HRESULT 0x80632095 marks group discovery found member candidates, but none could accept the connection attempt. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PeerGroupConnect, PeerGroupConnectByAddress and remote member diagnostics that returned the HRESULT.
- Preserve candidate endpoints, per-endpoint connect result, listener/firewall state, member group status and authentication events.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: connect by the IPv6 address of one known active member and compare with aggregate PNRP-driven connection.
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.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the group membership described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original GMC trust chain was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_NO_MEMBERS_FOUND differs because it proves candidates existed; no-members-found stops earlier at discovery. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Repair listener, firewall, capacity or credential state on at least one discovered member instead of changing the group name. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- 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.