| Previous | Next |
| ERROR_IPSEC_IKE_NO_PUBLIC_KEY | ERROR_IPSEC_IKE_PROCESS_ERR_SA |
ERROR_IPSEC_IKE_PROCESS_ERR
The failure occurred while handling an error payload
IKE uses notification payloads to report protocol and negotiation conditions. This status is not the original peer error itself; it indicates that Windows had trouble processing an error payload after receiving or constructing the exchange. The distinction matters because the packet can contain a valid failure notification whose contents, exchange context, or referenced SA cannot be handled as expected.
Start with the packet or trace immediately before this status. In IKEv1, Notify payloads are defined by ISAKMP/IKE; IKEv2 also uses Notify payloads and ties many of them to a particular exchange. An unrelated message ID, stale SA, malformed notification, or implementation extension can change how the error is interpreted.
What to inspect
- Identify the Notify type and exchange that preceded the processing error.
- Check whether the peer simultaneously deleted or rekeyed the parent SA.
- Do not report only this wrapper code when a packet trace contains the actual peer notification.
References
- IETF RFC 2409: Internet Key Exchange v1
- IETF RFC 7296: IKEv2
- Microsoft Open Specifications: MS-IKEE index
Looking for a different code? Search another status or error code.