| Previous | Next |
| FWP_E_TXN_IN_PROGRESS | FWP_E_SESSION_ABORTED |
FWP_E_TXN_ABORTED
FWP_E_TXN_ABORTED reports that the active explicit WFP transaction was forcibly canceled. No caller should infer from earlier successful API returns that its whole policy update took effect; the transaction boundary determines whether the staged change set became visible.
Preserve the failure context
- Record the first API failure and any Base Filtering Engine or RPC condition that preceded the abort.
- Discard in-memory assumptions about newly added IDs or changed objects until the engine state has been re-read.
- Separate retryable engine contention from configuration errors such as an invalid layer, type, or action.
Recovery
Close or reuse the session according to its state, start a new explicit transaction only after the cause is understood, and rebuild the intended policy set from declarative data. Retrying individual interior calls without re-establishing transaction state can create a result different from the original all-or-nothing update.
Microsoft: WFP error codes · Microsoft: automatic and explicit transaction behavior · Microsoft: clean up partial results with transactions
Looking for a different code? Search another status or error code.