> Source: [sk109797](https://support.checkpoint.com/results/sk/sk109797)

# sk109797 - Traffic is dropped without any logs; Policy installation fails with "fwk_atomic_load_prepare: fwk_mtcounter_prepare failed"

| Property | Value |
|----------|-------|
| Solution ID | sk109797 |
| Date Created | 2016-01-25 |
| Last Modified | 2023-03-22 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Connectivity issues. There are no relevant logs in SmartView Tracker.
* IPS kernel debug ('`fw ctl debug -m fw + aspii tcpstr`') during connection attempts shows:  
  *

    ```
    
    ;FW - 1 mtcounter_id_get: Error counter id XXX is outside of range 0-0.;
    ;FW-1: fw_brute_force_detect: KFUNC_BF_CHECK_ATTACK could not find attack counter.;
    ... ...
    ;aspii_process_data_ex: Finished running the handler after 1 runs.
    ... ...
    ;aspii_handle_action: Protection cifs_bf_code Setting action 'reject' on matrix.;
    ;psl_process_data: processing function for app ...[ASPII_MT] returned STOP_AND_REJECT;
    ```

  *

    ```
     
    ;FW - 1 mtcounter_id_get: Error counter id XXX is outside of range 0-0.;
    ;FW-1: fw_mtcounter_get_value: could not abtain counter id XXX;
    ```

* Policy installation fails with "`Load on Module failed`".  

  Kernel debug ('`fw ctl debug -m fw + filter`') during policy installation shows:

  ```
  
  ;FW-1: Attempting to create an already existing table: fw_mtcounter_sync_htab_table (XXX);
  ;FW-1: failed to create fw_mtcounter_sync_htab_table table;
  ;fwk_atomic_load_prepare: fwk_mtcounter_prepare failed;
  ```

## Cause

Wrong handling of some kernel tables.

## Solution

Follow these steps:

1. Perform manual IPS update and install the policy.

   If the issue persists, then proceed to the next step.
2. [Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue.

   This fix is included in:
   * [Jumbo Hotfix Accumulator for R77.30](http://supportcontent.checkpoint.com/solutions?id=sk106162) - since *Take_128*

   For **other [supported](http://www.checkpoint.com/support-services/support-life-cycle-policy/index.html) versions** , [Check Point Support](http://www.checkpoint.com/support-services/contact-support/index.html) can supply a **Hotfix** .  
   A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
   For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

   **Hotfix installation instructions for Gaia/SecurePlatform/IPSO OS:**
   1. Hotfix has to be installed on ***Security Gateway***.

      **Note:** In cluster environment, this procedure must be performed on *all* members of the cluster.   

   2. Transfer the hotfix package to the machine (into some directory, e.g., */some_path_to_fix/* ).   

   3. Unpack the hotfix package:

      ***\[Expert@HostName\]# cd /some_path_to_fix/***   
      ***\[Expert@HostName\]# tar -zxvf fw1_wrapper_\<HOTFIX_NAME\>.tgz***   

   4. Install the hotfix:

      ***\[Expert@HostName\]# ./fw1_wrapper_\<HOTFIX_NAME\>***
      **Note:** The script will stop all of Check Point services (*cpstop* ) - read the output on the screen.   

   5. Reboot the machine.  

   6. Connect with SmartDashboard to Security Management Server / Domain Management Server.  

   7. Install policy.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content