| 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 means that the peer component reached the point where it needed a Windows service or hosted peer component, but that dependency could not be started. The relevant API boundary includes 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 |
|---|---|
| Raw input | Preserve Service Control Manager events, service configuration, dependency chain, logon context, process elevation state, startup type and the underlying Win32 service error. |
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.
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.
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.
Technical references
Looking for a different code? Search another status or error code.