| Previous | Next |
| CO_E_CANT_REMOTE | CO_E_WRONG_SERVER_IDENTITY |
CO_E_BAD_SERVER_NAME
CO_E_BAD_SERVER_NAME identifies a bad remote-machine name at the activation-selection stage. The code is about the server name passed to COM or obtained from configuration; it is not the same as a host that was validly named but later became unreachable.
Where the name can come from
A client can provide a machine name through COSERVERINFO when it uses CoCreateInstanceEx. When no such structure is supplied, the class AppID can provide RemoteServerName. Check both the caller and the deployed registry state before troubleshooting RPC transport, firewall rules, or server startup.
Useful checks
- Log the CLSID and the exact target chosen by the client, including whether it came from code or the AppID key.
- Verify that the CLSID maps to the intended AppID and that configuration does not contain a stale or malformed remote target.
- After correcting the name, test the remote activation path separately from local activation; the two paths use different registration and security decisions.
References
- Microsoft: AppID key and RemoteServerName
- Microsoft: COM class objects, CLSIDs, and remote locations
- Microsoft: generic COM error codes
Looking for a different code? Search another status or error code.