| Previous | Next |
| CO_E_RUNAS_LOGON_FAILURE | CO_E_START_SERVICE_FAILURE |
CO_E_LAUNCH_PERMSSION_DENIED
CO_E_LAUNCH_PERMSSION_DENIED indicates an authorization decision during COM activation. The client is not permitted to launch the server selected for the requested class. The constant name contains the historical spelling PERMSSION; use that exact spelling when matching the HRESULT or the Windows header.
Launch permission is not call permission
COM separates permissions to start or activate a server from permissions to call a server that is already running. AppID configuration can contain a LaunchPermission security descriptor, and DCOM distinguishes Local Launch, Remote Launch, Local Activation, and Remote Activation rights. Starting the executable manually may hide the symptom without repairing the activation policy.
Safe way to investigate
- Identify the CLSID, AppID, client identity, and whether the request is local or remote.
- Review the application’s launch and activation permissions with DCOM configuration tools or the AppID security descriptor.
- Grant only the required local or remote launch/activation right to the intended principal; avoid solving the error by granting broad access to all users.
References
- Microsoft: AppID key and LaunchPermission
- Microsoft: DCOM launch and activation rights
- Microsoft: configuring COM security with DCOMCNFG
Looking for a different code? Search another status or error code.