| Previous | Next |
| PEER_E_UNSUPPORTED_VERSION | PEER_E_GROUP_IN_USE |
PEER_E_GROUP_NOT_READY
Which peer contract was rejected
PEER_E_GROUP_NOT_READY — HRESULT 0x80632091 marks the operation requires an online group connection, but the local member has only opened/joined the group or has become disconnected. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGroupOpen/Join, PeerGroupConnect, PeerGroupGetStatus and group events.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve PeerGroupGetStatus, connect events, member/neighbor counts, PNRP result, local group handle and the operation attempted before online state. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Wait for connected group status, run the operation, then compare with the same call immediately after PeerGroupOpen. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_NO_MEMBERS_FOUND differs because group-not-ready is local lifecycle state; no-members-found is a completed connection search with no active members. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Separate local database-open state from online group state and queue network-dependent actions until connection is confirmed. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical 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.