| Previous | Next |
| PEER_E_IDENTITY_DELETED | PEER_E_CANNOT_CONVERT_PEER_NAME |
PEER_E_SERVICE_NOT_AVAILABLE
Diagnostic boundary for PEER_E_SERVICE_NOT_AVAILABLE
HRESULT 0x806320A1 marks the Peer Collaboration/People Near Me infrastructure is unavailable to the caller, including the documented restriction on use from an elevated 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 PeerCollabStartup and Peer Collaboration API calls, or reconstructed from cached text or another process?
- Preserve process integrity/elevation, interactive user session, collaboration startup result, feature/service state and the exact API call.
- 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 Collaboration provides serverless presence, contacts, endpoint subscriptions and invitations. Its operations depend on an interactive user context, explicit sign-in scopes and firewall/privacy consent.
Controlled comparison
Run the same minimal collaboration startup/sign-in test as the unelevated interactive user and compare with the elevated process. 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 invitation workflow; repeated network retries add no evidence. |
The call advances to PEER_E_CANNOT_START_SERVICE | PEER_E_CANNOT_START_SERVICE differs because cannot-start-service is dependency startup failure; service-not-available can be an intentional execution-context restriction. |
| 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
Move collaboration calls to an appropriate user-context process and verify the feature is installed and available; do not lower system security globally. 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: About the Peer Collaboration API — it uses this source for the documented peer boundary.
- Microsoft: Collaboration API functions
- Microsoft: People Near Me requirements
- Microsoft: Windows Firewall rules
Looking for a different code? Search another status or error code.