| Previous | Next |
| PEER_E_INVITE_RESPONSE_NOT_AVAILABLE | PEER_E_PRIVACY_DECLINED |
PEER_E_NOT_SIGNED_IN
Diagnostic boundary for PEER_E_NOT_SIGNED_IN
HRESULT 0x80637003 marks the collaboration operation requires presence sign-in for the requested scope, but the local user is not signed in. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerCollabSignIn, PeerCollabSignOut and presence/invitation calls, or reconstructed from cached text or another process?
- Preserve requested PEER_SIGNIN_FLAGS/scope, PeerCollabGetSigninOptions result, prior sign-in HRESULT, user session and sign-out events.
- 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
Sign in to only the required People Near Me or Internet presence scope and repeat the operation in the same user session. 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_PRIVACY_DECLINED | PEER_E_PRIVACY_DECLINED differs because not-signed-in can be corrected by sign-in; privacy-declined records that the user refused the enabling consent flow. |
| 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
Make sign-in an explicit user-visible state and do not assume PeerCollabStartup also publishes presence. 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.