What does NTSTATUS 0xC000020F (STATUS_TRANSACTION_ABORTED) mean?

 
Previous Next
STATUS_TOO_MANY_NODES STATUS_TRANSACTION_TIMED_OUT

STATUS_TRANSACTION_ABORTED

This transport transaction status is not a KTM or TxF transaction result

The Microsoft NTSTATUS catalog explicitly describes STATUS_TRANSACTION_ABORTED in transport terms. Its code sits beside transport connection and request statuses, well before the separate Transaction Manager facility values used by KTM/TxF. Do not route this error into database or filesystem-transaction diagnostics merely because the word transaction appears in the name.

Public Windows documentation does not expose the internal transaction record behind this status, so the producer and request context are essential. Legacy TDI illustrates the relevant transport architecture: requests are issued against connection, address, or control objects and may be pending while a transport talks to a remote peer. An abort can therefore be correlated with disconnect/reset, driver cancellation, lower-network errors, or explicit teardown, but the NTSTATUS value alone does not identify which event initiated the abort.

Capture the request identifier/token used by the producer, endpoint state, abort/cancel reason, and the first preceding transport event. If a timeout appears later in the log, do not assume it caused this code; an aborted request and a request that waited until its deadline are distinct statuses in the same family. Retries should only occur if the caller can safely issue the operation again and has established a new valid request state.

What to inspect

  • Record the first abort, cancel, disconnect, or lower-transport event before the status.
  • Keep the producer-specific request ID/token with endpoint state and peer address.
  • Verify retry safety instead of treating every transport abort as idempotent.

References

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