| Previous | Next |
| CO_E_LAUNCH_PERMSSION_DENIED | CO_E_REMOTE_COMMUNICATION_FAILURE |
CO_E_START_SERVICE_FAILURE
CO_E_START_SERVICE_FAILURE means that COM selected a service-hosted server and the service could not be started. This is not a LocalServer32 executable-start error: COM service activation is based on the LocalService registration and the matching Windows service installation.
How service activation is registered
A COM object can be installed as a Windows service by setting LocalService to the service name under the AppID key and performing standard service installation. When that service model is present, COM uses the service rather than the ordinary local-server executable registration.
What to verify
- Follow the CLSID-to-AppID mapping and check that
LocalServicenames the intended service entry underHKLM\System\CurrentControlSet\Services. - Use the service’s own startup diagnostics and event records to identify why the Service Control Manager could not start it.
- Do not try to repair a service account by editing the AppID
RunAsvalue; Microsoft documents thatRunAsis not used for service-configured servers.
References
- Microsoft: LocalService
- Microsoft: installing a COM service application
- Microsoft: RunAs and service-hosted servers
Looking for a different code? Search another status or error code.
