| Previous | Next |
| CO_E_RUNAS_CREATEPROCESS_FAILURE | CO_E_LAUNCH_PERMSSION_DENIED |
CO_E_RUNAS_LOGON_FAILURE
CO_E_RUNAS_LOGON_FAILURE means that the server identity was configured but COM could not establish the logon session needed to start the server. Unlike CO_E_RUNAS_SYNTAX, the account specification has already passed the basic syntax check.
What COM requires
For a non-service COM server configured with RunAs, COM obtains the user name from the AppID key and uses stored credentials to create the server’s logon session. Microsoft also notes that a user account used by a DCOM server must have the Log on as a batch job right. Service-hosted COM servers use service-account configuration instead of AppID RunAs.
Diagnostic sequence
- Resolve the CLSID to its AppID, then verify the intended account with DCOM configuration rather than copying credentials into application settings.
- Check the account’s logon policy and current validity before changing COM registration.
- Keep service activation and RunAs activation separate: a class configured with
LocalServiceshould be diagnosed through the Windows service configuration and service-start result.
References
Looking for a different code? Search another status or error code.