NTSTATUS 0xC0020041 (RPC_NT_CANNOT_SUPPORT): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

RPC runtime rejected an operation that the selected binding, protocol sequence, or endpoint cannot support.

Previous	Next
RPC_NT_INVALID_NAF_ID	RPC_NT_NO_CONTEXT_AVAILABLE

RPC_NT_CANNOT_SUPPORT

Unsupported operation in the RPC runtime

RPC_NT_CANNOT_SUPPORT belongs to the Windows RPC runtime NTSTATUS facility. For RPC_NT_CANNOT_SUPPORT, mS-RPCE extends the DCE/RPC model: generated stubs marshal parameters, the runtime binds to an endpoint and protocol sequence, and security or transport failures can be returned as RPC facility status values.

This status is returned by the RPC runtime when the call is valid enough to reach RPC dispatch logic, but the selected operation is not available in the current RPC configuration. It is different from an unknown endpoint or an unavailable server: the endpoint path exists far enough for the runtime to decide that this feature is not supported.

Useful evidence is the protocol sequence, binding handle type, transfer syntax, authentication package, and the server interface version. A common mistake is to retry the same call over the same binding; that only repeats the unsupported combination.

What to check for RPC_NT_CANNOT_SUPPORT

Compare the client binding string with the server protocol sequences actually registered.
Check whether the operation depends on async RPC, pipes, callbacks, or security services that the server did not advertise.
If several transports are available, test the same interface over a simpler local or named-pipe binding to separate transport limits from interface limits.

References for RPC_NT_CANNOT_SUPPORT

Looking for a different code? Search another status or error code.