| Previous | Next |
| PEER_E_GROUP_IN_USE | PEER_E_NO_MEMBERS_FOUND |
PEER_E_INVALID_GROUP
Where the peer stack rejects the operation
PEER_E_INVALID_GROUP — HRESULT 0x80632093 marks the HGroup handle is invalid or the referenced group has been marked for deletion. Treat it as a group membership result rather than a generic peer-networking failure.
Evidence to preserve before retrying
- Record the first failing surface among PeerGroupCreate/Join/Open, PeerGroupClose and PeerGroupDelete.
- Preserve handle creation call, identity and group peer name, delete/close events, thread ownership and the first call after invalidation.
- 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
Repeat with a fresh handle returned by PeerGroupOpen and compare with use after PeerGroupDelete or PeerGroupClose. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Stage | Question |
|---|---|
| Before the API | Was the required GMC trust chain obtained in this process and user context? |
| After correction | stop work before deleting/closing the group and invalidate every cached handle or wrapper object. |
Neighboring result
PEER_E_GROUP_IN_USE differs because invalid-group rejects the handle/object; group-in-use rejects an operation because a valid group is still active. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Stop work before deleting/closing the group and invalidate every cached handle or wrapper object. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
References
Looking for a different code? Search another status or error code.