| Previous | Next |
| CO_E_SCM_RPC_FAILURE | CO_E_SERVER_EXEC_FAILURE |
CO_E_BAD_PATH
This code places the first failure in registered COM server path resolution. Operationally, the activation metadata points to a malformed, unavailable, or contextually unusable object/server path.
The contract behind the HRESULT
CO_E_SERVER_EXEC_FAILURE means the server command was reached but did not establish COM service; CO_E_BAD_PATH points earlier to path resolution.
Diagnostic worksheet
- The resolved LocalServer32, service, surrogate, or moniker path exactly as COM reads it
- Environment expansion, quotes, working directory assumptions, drive mappings, and UNC accessibility
- Caller/server bitness and the registry view containing the path
- File existence, signature, ACL, and loader access under the activation identity
Identifiers, timestamps, versions, counts, state flags, hashes, and redacted paths normally provide enough correlation. Keep credentials, private keys, message bodies, recovery material, and personal data out of routine incident logs.
Reproduce the condition safely
- Launch the registered command line under the configured identity without changing its quoting.
- Replace a mapped drive with the equivalent stable local or UNC path in a test registration.
- Compare registry views from 32-bit and 64-bit clients.
Closing the incident
Apply the smallest change that addresses the first rejected condition: Store a fully qualified, correctly quoted, identity-accessible path and avoid per-user drive mappings in machine-wide activation metadata.
Close the incident only when a cold activation resolves the same path from every supported client bitness and survives reboot without environment-dependent lookup.
Technical references
The details above are grounded in the following Microsoft specifications and API documentation:
Looking for a different code? Search another status or error code.