What does NTSTATUS 0xC0000215 (STATUS_TRANSACTION_INVALID_TYPE) mean?

 
Previous Next
STATUS_TRANSACTION_INVALID_ID STATUS_NOT_SERVER_SESSION

STATUS_TRANSACTION_INVALID_TYPE

The request kind is invalid even before request-specific processing can proceed

STATUS_TRANSACTION_INVALID_TYPE is the type-validation member of the old transport transaction status family. Microsoft explicitly says the transport does not recognize the transaction request type. The failure should therefore be diagnosed at dispatch/protocol decoding, before treating it as a peer timeout, missing release, or unmatched response token.

Legacy TDI is a useful public example of typed transport dispatch. A transport driver receives internal device-control requests and interprets them according to both the TDI minor function and the kind/state of the file object, which can represent an address, connection endpoint, or control channel. The exact private transaction type behind this NTSTATUS is not documented as a TDI minor function, so the page does not equate the two. The architecture nevertheless shows why “valid request data sent to the wrong object or dispatcher” can fail as a type problem.

Preserve the request-type field, interface/version number, object type, provider identity, and raw request buffer. Compare producer and consumer headers or protocol versions. A stale binary using a type introduced by a different provider revision is more relevant than network reachability. Also distinguish STATUS_TRANSACTION_INVALID_ID: a recognized type can still carry an invalid ID, while this status says the request kind itself is not recognized.

What to inspect

  • Log request type and interface/version before any compatibility translation.
  • Confirm the request was dispatched on the correct address, connection, or control object.
  • Compare producer and transport-provider definitions for the request-type field.

References

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