What does Windows error code 1716 (RPC_S_UNKNOWN_MGR_TYPE) mean?

 
Previous Next
RPC_S_NOT_LISTENING RPC_S_UNKNOWN_IF

RPC_S_UNKNOWN_MGR_TYPE

The interface exists, but the requested manager implementation does not

RPC_S_UNKNOWN_MGR_TYPE appears in servers that use RPC object types and multiple manager entry-point vectors. The runtime uses an object's type UUID to choose the manager EPV registered for the interface. If that type is not known for the interface, the runtime cannot dispatch the call to an implementation.

This is not the same as RPC_S_UNKNOWN_IF. An interface UUID can be registered correctly while a particular manager type is missing.

How to diagnose it

  • Capture the interface UUID, object UUID, and resolved type UUID for the failed call.
  • Compare the type UUID with every MgrTypeUuid used in RpcServerRegisterIf*.
  • Verify that an object inquiry callback does not return a stale or unintended type after configuration reload.
  • When only one manager implementation is needed, use the nil type association consistently instead of manufacturing per-object types.

The corrective action is to align object-to-type mapping with interface manager registration. Endpoint mapper changes will not create the missing manager EPV.

References


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