| Previous | Next |
| STATUS_FWP_TXN_IN_PROGRESS | STATUS_FWP_SESSION_ABORTED |
STATUS_FWP_TXN_ABORTED
The transaction lock was released after a forced rollback
STATUS_FWP_TXN_ABORTED means the current explicit transaction is no longer valid. WFP can forcibly abort a transaction that holds its lock beyond the documented limit; when that happens, the next call made within that transaction reports this status.
Treat all uncommitted operations in that transaction as rolled back. Do not continue issuing filter-add or delete calls on the same transaction handle. Instead, capture the timeout cause, re-open a transaction, re-enumerate the relevant policy, and rebuild only the changes that are still required.
What to measure
- Transaction start, last successful operation, and elapsed lock ownership time.
- Long RPC calls, user interaction, or external I/O performed while the transaction was open.
- Whether the affected policy objects were actually committed before the forced abort.
- Whether a shorter transaction can stage data before acquiring the WFP lock.
References
- Microsoft: WFP error codes
- Microsoft: WFP sessions, transactions, and object lifetimes
- Microsoft: WFP object model
Looking for a different code? Search another status or error code.