| Previous | Next |
| PEER_E_IPV6_NOT_INSTALLED | PEER_E_CANNOT_START_SERVICE |
PEER_E_NOT_INITIALIZED
Diagnostic boundary for PEER_E_NOT_INITIALIZED
HRESULT 0x80630002 marks a Peer API was called before the matching infrastructure startup routine completed for 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 PeerGraphStartup, PeerGroupStartup, PeerCollabStartup and their corresponding shutdown functions, or reconstructed from cached text or another process?
- Preserve thread and process ID, the exact startup function and version structure, its HRESULT, shutdown ordering, module unload events, and the first later 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?
The Windows Peer Infrastructure is composed of Graphing, Grouping, Identity Manager, PNRP and Collaboration APIs. Initialization and platform prerequisites must be established before object-specific calls can be interpreted.
Controlled comparison
Run a minimal startup-call-operation-shutdown sequence in one process and then deliberately repeat the operation without startup. 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 startup boundary; repeated network retries add no evidence. |
The call advances to PEER_E_INVALID_GRAPH | PEER_E_INVALID_GRAPH differs because an invalid graph handle means initialization occurred but the supplied object handle is not usable. |
| 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 startup ownership explicit and pair every successful startup with shutdown only after all graph, group, collaboration and enumeration handles are closed. 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: Common Peer Infrastructure return codes — it uses this source for the documented peer boundary.
- Microsoft: What is the Peer Infrastructure?
- Microsoft: Programming considerations for Peer-to-Peer applications
Looking for a different code? Search another status or error code.