WFP Error Codes
Header: winerror.h
Windows Filtering Platform (WFP) specific error codes are as follows.
| Symbolic | Code | Description |
|---|---|---|
| FWP_E_CALLOUT_NOT_FOUND | 0x80320001 | The callout does not exist. |
| FWP_E_CONDITION_NOT_FOUND | 0x80320002 | The filter condition does not exist. |
| FWP_E_FILTER_NOT_FOUND | 0x80320003 | The filter does not exist. |
| FWP_E_LAYER_NOT_FOUND | 0x80320004 | The layer does not exist. |
| FWP_E_PROVIDER_NOT_FOUND | 0x80320005 | The provider does not exist. |
| FWP_E_PROVIDER_CONTEXT_NOT_FOUND | 0x80320006 | The provider context does not exist. |
| FWP_E_SUBLAYER_NOT_FOUND | 0x80320007 | The sub-layer does not exist. |
| FWP_E_NOT_FOUND | 0x80320008 | The object does not exist. The [IPsecSaContext*](fwp-ipsec-functions.md) functions return this error if the SA context ID is not found. |
| FWP_E_ALREADY_EXISTS | 0x80320009 | An object with that GUID or LUID already exists. |
| FWP_E_IN_USE | 0x8032000A | The object is referenced by other objects, so it cannot be deleted. |
| FWP_E_DYNAMIC_SESSION_IN_PROGRESS | 0x8032000B | The call is not allowed from within a dynamic session. |
| FWP_E_WRONG_SESSION | 0x8032000C | The call was made from the wrong session, so it cannot be completed. |
| FWP_E_NO_TXN_IN_PROGRESS | 0x8032000D | The call must be made from within an explicit transaction. |
| FWP_E_TXN_IN_PROGRESS | 0x8032000E | The call is not allowed from within an explicit transaction. |
| FWP_E_TXN_ABORTED | 0x8032000F | The explicit transaction has been forcibly canceled. |
| FWP_E_SESSION_ABORTED | 0x80320010 | The session has been canceled. The session handle needs to be closed by calling [**FwpmEngineClose0**](/windows/desktop/api/Fwpmu/nf-fwpmu-fwpmengineclose0), even though it is no longer valid; otherwise, the client-side state will be leaked. A new session should be created by calling [**FwpmEngineOpen0**](/windows/desktop/api/Fwpmu/nf-fwpmu-fwpmengineopen0). |
| FWP_E_INCOMPATIBLE_TXN | 0x80320011 | The call is not allowed from within a read-only transaction. |
| FWP_E_TIMEOUT | 0x80320012 | The call timed out while waiting to acquire the transaction lock. |
| FWP_E_NET_EVENTS_DISABLED | 0x80320013 | The collection of network diagnostic events is disabled. |
| FWP_E_INCOMPATIBLE_LAYER | 0x80320014 | The operation is not supported by the specified layer. |
| FWP_E_KM_CLIENTS_ONLY | 0x80320015 | The call is allowed for kernel-mode callers only. |
| FWP_E_LIFETIME_MISMATCH | 0x80320016 | The call tried to associate two objects with incompatible lifetimes. See [Object Management](object-management.md) for more information on object lifetime and object association. |
| FWP_E_BUILTIN_OBJECT | 0x80320017 | The object is built-in, so it cannot be deleted. |
| FWP_E_TOO_MANY_CALLOUTS | 0x80320018 | The maximum number of callouts has been reached. At most, 100,000 callouts can be registered at the same time. |
| FWP_E_NOTIFICATION_DROPPED | 0x80320019 | A notification could not be delivered because a message queue is at its maximum capacity. |
| FWP_E_TRAFFIC_MISMATCH | 0x8032001A | The network traffic parameters do not match those for the security association context. [**IPsecSaContextGetSpi0**](/windows/desktop/api/Fwpmu/nf-fwpmu-ipsecsacontextgetspi0) can be called multiple times, but the caller must specify the same [**IPSEC_TRAFFIC0**](/windows/desktop/api/Ipsectypes/ns-ipsectypes-ipsec_traffic0) each time. This error is returned if a subsequent call supplies a different **IPSEC_TRAFFIC0**. |
| FWP_E_INCOMPATIBLE_SA_STATE | 0x8032001B | The call is not allowed for the current security association (SA) state. The SA context functions must be called in a specific order: - [**IPsecSaContextCreate0**](/windows/desktop/api/Fwpmu/nf-fwpmu-ipsecsacontextcreate0) - [**IPsecSaContextGetSpi0**](/windows/desktop/api/Fwpmu/nf-fwpmu-ipsecsacontextgetspi0) - [**IPsecSaContextAddInbound0**](/windows/desktop/api/Fwpmu/nf-fwpmu-ipsecsacontextaddinbound0) - [**IPsecSaContextAddOutbound0**](/windows/desktop/api/Fwpmu/nf-fwpmu-ipsecsacontextaddoutbound0) This error is returned if they are called out of order. |
| FWP_E_NULL_POINTER | 0x8032001C | A required pointer is null. |
| FWP_E_INVALID_ENUMERATOR | 0x8032001D | An enumerator value in a structure is out of range. |
| FWP_E_INVALID_FLAGS | 0x8032001E | The flags field contains an invalid value. |
| FWP_E_INVALID_NET_MASK | 0x8032001F | A network mask is not valid. |
| FWP_E_INVALID_RANGE | 0x80320020 | An [**FWP_RANGE0**](/windows/desktop/api/Fwptypes/ns-fwptypes-fwp_range0) structure is not valid. |
| FWP_E_INVALID_INTERVAL | 0x80320021 | The time interval is not valid. |
| FWP_E_ZERO_LENGTH_ARRAY | 0x80320022 | An array that must contain at least one element has zero length. |
| FWP_E_NULL_DISPLAY_NAME | 0x80320023 | The **displayData.name** field cannot be null. |
| FWP_E_INVALID_ACTION_TYPE | 0x80320024 | The action type is not one of the allowed action types for a filter. |
| FWP_E_INVALID_WEIGHT | 0x80320025 | The filter weight is not valid. See [Filter Weight Assignment](filter-weight-assignment.md) for more information. |
| FWP_E_MATCH_TYPE_MISMATCH | 0x80320026 | A filter condition contains a match type that is not compatible with the operands. See [**FWP_MATCH_TYPE**](/windows/desktop/api/Fwptypes/ne-fwptypes-fwp_match_type) for more information. |
| FWP_E_TYPE_MISMATCH | 0x80320027 | An [**FWP_VALUE0**](/windows/desktop/api/Fwptypes/ns-fwptypes-fwp_value0) structure or an [**FWPM_CONDITION_VALUE0**](/windows/desktop/api/Fwptypes/ns-fwptypes-fwp_condition_value0) structure is of the wrong type. |
| FWP_E_OUT_OF_BOUNDS | 0x80320028 | An integer value is outside the allowed range. |
| FWP_E_RESERVED | 0x80320029 | A reserved field is nonzero. |
| FWP_E_DUPLICATE_CONDITION | 0x8032002A | A filter cannot contain multiple conditions operating on a single field. |
| FWP_E_DUPLICATE_KEYMOD | 0x8032002B | A policy cannot contain the same keying module more than once. |
| FWP_E_ACTION_INCOMPATIBLE_WITH_LAYER | 0x8032002C | The action type is not compatible with the layer. |
| FWP_E_ACTION_INCOMPATIBLE_WITH_SUBLAYER | 0x8032002D | The action type is not compatible with the sub-layer. |
| FWP_E_CONTEXT_INCOMPATIBLE_WITH_LAYER | 0x8032002E | The raw context or the provider context is not compatible with the layer. |
| FWP_E_CONTEXT_INCOMPATIBLE_WITH_CALLOUT | 0x8032002F | The raw context or the provider context is not compatible with the callout. |
| FWP_E_INCOMPATIBLE_AUTH_METHOD | 0x80320030 | The authentication method is not compatible with the policy type. |
| FWP_E_INCOMPATIBLE_DH_GROUP | 0x80320031 | The Diffie-Hellman group is not compatible with the policy type. |
| FWP_E_EM_NOT_SUPPORTED | 0x80320032 | An IKE policy cannot contain an Extended Mode policy. |
| FWP_E_NEVER_MATCH | 0x80320033 | The enumeration template or subscription will never match any objects. |
| FWP_E_PROVIDER_CONTEXT_MISMATCH | 0x80320034 | The provider context is of the wrong type. |
| FWP_E_INVALID_PARAMETER | 0x80320035 | The parameter is incorrect. Possible reasons for this error: - [**FwpmIPsecTunnelAdd0**](/windows/desktop/api/Fwpmu/nf-fwpmu-fwpmipsectunneladd0) was called without setting the flag **FWPM_TUNNEL_FLAG_POINT_TO_POINT** and with conditions other than local/remote address. - An invalid Unicode string, or a Unicode string that contains unprintable characters. |
| FWP_E_TOO_MANY_SUBLAYERS | 0x80320036 | The maximum number of sublayers has been reached. WFP supports at most 2 6 sublayers. |
| FWP_E_CALLOUT_NOTIFICATION_FAILED | 0x80320037 | The notification function for a callout returned an error. |
| FWP_E_INVALID_AUTH_TRANSFORM | 0x80320038 | The IPsec authentication transform is not valid. |
| FWP_E_INVALID_CIPHER_TRANSFORM | 0x80320039 | The IPsec cipher transform is not valid. |
| 57 entries | ||
Article text from the Win32 documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.