| Previous | Next |
| CO_E_BAD_SERVER_NAME | CO_E_OLE1DDE_DISABLED |
CO_E_WRONG_SERVER_IDENTITY
CO_E_WRONG_SERVER_IDENTITY means that COM found an identity conflict while resolving the class server. The problem is not a general file-permission failure: it concerns the security identity configured for the COM application and the identity or activation context required for this request.
Identity is part of COM activation
Out-of-process COM servers can be associated with an AppID. That AppID centralizes deployment and security settings, including RunAs, while service-hosted servers use LocalService and the service’s own account configuration. A class that is intentionally configured for one identity should not be treated as interchangeable with the caller’s process identity.
How to diagnose without weakening the setup
- Identify the CLSID, then inspect its AppID association and the selected server model: executable, service, or remote server.
- Compare the configured identity with the required deployment model before changing credentials or DCOM permissions.
- Separate this result from
CO_E_RUNAS_LOGON_FAILURE, which concerns failure to log on with a configured identity, and from launch-permission denial, which concerns authorization of the client.
References
- Microsoft: AppID key
- Microsoft: RunAs configuration for COM servers
- Microsoft: COM servers installed as services
Looking for a different code? Search another status or error code.