Site icon EfmSoft

What does NTSTATUS 0xC0000212 (STATUS_TRANSACTION_NO_MATCH) mean?

 
Previous Next
STATUS_TRANSACTION_NO_RELEASE STATUS_TRANSACTION_RESPONDED

STATUS_TRANSACTION_NO_MATCH

The transport has a token, but no pending transaction matches it

STATUS_TRANSACTION_NO_MATCH is a correlation failure. Microsoft describes a transport searching for a transaction that matches a specific token and finding none. The status does not mean DNS lookup failure, certificate-name mismatch, or failure to find a server. The “match” is between transport transaction state and a producer-specific token.

Public transport documentation does not define that token format, so preserve it in the component that reports the status. Legacy TDI shows that request-specific information can be carried between a transport driver's internal routines while state is also attached to address, connection, or control objects. A stale token after reconnect, duplicate response, transaction-table cleanup, or request delivered to the wrong endpoint context are all conditions worth testing, but they are hypotheses until the producer log proves the sequence.

Compare this code with STATUS_TRANSACTION_INVALID_ID. “No match” implies a lookup was attempted for a token and no current transaction corresponded to it; “invalid ID” says the request identifier itself is not recognized by the transport. Capture token value, connection object, request type, generation/sequence information, and transaction creation/removal timestamps. A packet capture without the provider's token mapping may be insufficient, especially for an internal transport protocol.

What to inspect

References


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

Exit mobile version