| Previous | Next |
| PEER_E_NOT_INITIALIZED | PEER_E_NOT_LICENSED |
PEER_E_CANNOT_START_SERVICE
Which peer contract was rejected
PEER_E_CANNOT_START_SERVICE — HRESULT 0x80630003 marks the peer component reached the point where it needed a Windows service or hosted peer component, but that dependency could not be started. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerGraphStartup, PeerGroupStartup, PeerCollabStartup and Service Control Manager diagnostics.
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.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve Service Control Manager events, service configuration, dependency chain, logon context, process elevation state, startup type and the underlying Win32 service error. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Start the relevant peer feature through its documented API in a clean user session and compare the service transition with a direct service start attempt. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_SERVICE_NOT_AVAILABLE differs because service startup failure occurs while bringing up infrastructure, whereas service-not-available can also reflect an unsupported collaboration execution context. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Repair the disabled, missing or failing peer component and its dependencies; do not hide the failure by repeatedly recreating graph or group databases. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical 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.