How To Fix The `Failed to set Engine's Packet Filter Loadstate` Error

Follow

Summary

This knowledgebase article contains a workaround that can be used to avoid the "Failed to set packet filter loadstate" error.

  

More Information

Symptoms

Neverfail Engine fails to start and the following message is logged in the nflogs:

[ClusterControllerThread](com.neverfail.controller.cluster.ClusterController) - Construction / Initialization failed - com.neverfail.controller.ControlException: Failed to set packet filter loadstate

Cause

When Neverfail starts it checks the Packet Filter loadstate. If the Packet Filter loadstate information is not found, the above error is logged and Neverfail ServerR2 service is stopped. This can happen as a result of the Neverfail Packet Filter Driver not being properly installed.

Resolution

Installing the Neverfail Packet Filter Driver correctly should fix this error.

If only this key is missing, it can be added manually

  1. From Start -> Run , open the Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE and create the following value:
    [HKEY_LOCAL_MACHINE\SOFTWARE\NFWfpPktFltr]:
    "LoadState"=DWORD:00000001
  3. Start Neverfail Engine.

Applies to 

Neverfail Continuity Engine

   * This KB article doesn't apply to Neverfail Heartbeat because Heartbeat has a different Packet Filter version then Engine.

 

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.