| Previous | Next |
| RPC_E_TOO_LATE | RPC_E_ACCESS_DENIED |
RPC_E_NO_GOOD_SECURITY_PACKAGES
No compatible COM security package is available
RPC_E_NO_GOOD_SECURITY_PACKAGES is HRESULT 2147549466 (0x8001011A) from winerror.h. The documented description is “No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server.” The relevant context is the COM/RPC call control, message filtering, apartment routing, marshaling, security negotiation, or remote object lifetime.
Where it is encountered
- Cross-apartment or cross-process COM method invocation and activation.
- STA message filtering, reentrancy, call cancellation, timeout, or retry handling.
- DCOM security initialization, proxy/stub marshaling, OBJREF processing, and server object lifetime.
The immediate focus is COM security negotiation with no installed, enabled, or mutually compatible authentication service for the requested settings.
What to verify
Verify that client and server package lists, principals, authentication level, domain state, and logon context are captured on both sides.
Correct handling and recovery
Enable a supported package, correct credentials and SPNs, or choose an allowed authentication service. Do not silently reduce security requirements.
Difference from nearby HRESULTs
It is negotiation capability failure; RPC_E_ACCESS_DENIED means a security context existed but authorization rejected access.
Practical scenario
A DCOM client requires Kerberos but the server SPN is missing and NTLM is disabled. Registration fixes the SPN and preserves the required authentication level.
References
Looking for a different code? Search another status or error code.