| Previous | Next |
| RPC_E_FULLSIC_REQUIRED | CO_E_FAILEDTOIMPERSONATE |
RPC_E_INVALID_STD_NAME
COM SSL principal is not a valid MSSTD name
RPC_E_INVALID_STD_NAME is HRESULT 2147549474 (0x80010122) from winerror.h. The documented description is “Principal name is not a valid MSSTD name.” 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 a standard principal-name string for secure RPC that has invalid prefix, escaping, certificate name, or syntax.
What to verify
Verify that the raw principal is compared with the documented msstd: form and the server certificate identity. Validate this condition using the owning API state, not an inferred UI symptom.
Difference from nearby HRESULTs
It is syntax validation; RPC_E_FULLSIC_REQUIRED says a syntactically valid but insufficient principal form was supplied.
Correct handling and recovery
Correct the principal at configuration generation, validate it before connection, and avoid constructing it from untrusted display names.
An unchanged retry loop can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.
Practical scenario
A configuration file contains an extra slash in an msstd: principal. Validation catches the typo before any remote activation attempt.
References
Looking for a different code? Search another status or error code.