| Previous | Next |
| PEER_E_GROUP_NOT_READY | PEER_E_INVALID_GROUP |
PEER_E_GROUP_IN_USE
Diagnostic boundary for PEER_E_GROUP_IN_USE
HRESULT 0x80632092 marks the group database is still open/connected during import, or the caller is trying to join a group that is already open in the process. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGroupClose, PeerGroupImportDatabase, PeerGroupJoin and PeerGroupOpen, or reconstructed from cached text or another process?
- Preserve open HGroup handles, connection status, import/join call, identity and group peer name, database path and close ordering.
- 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 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.
Controlled comparison
Close all group handles before import, or use PeerGroupOpen for an already joined group instead of joining it again. 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 GMC trust chain; repeated network retries add no evidence. |
The call advances to PEER_E_GRAPH_IN_USE | PEER_E_GRAPH_IN_USE differs because the graph code concerns raw graph database state; group-in-use also covers joining a group already open. |
| 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
Centralize group lifetime and make import an offline operation; do not race join/open calls across components. 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: 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.