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

# sk173248 - "problem with the Commit Function" during policy installation on a Standalone Firewall

| Property | Value |
|----------|-------|
| Solution ID | sk173248 |
| Date Created | 2021-05-20 |
| Last Modified | 2025-10-21 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server |
| Versions | R82, R81.20, R81.10 (EOS), R82, R81.20, R81 (EOS), R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * Following Jumbo Hotfix for R80.40 Take 94 or Take 102 installation on a Standalone Firewall, policy installation fails with:  
  `
  "Access policy fail : Reason: Load on Module failed - problem with the Commit Function"`.

* These logs are seen in fetch local debug on the gateway:  
  `
  # TDERROR_ALL_ALL=5 fw -d fetchlocal -d $FWDIR/state/__tmp/FW1/ > /var/log/fetch_debug.txt`  

  `

  [DATE TIME] malware_parser_parse: parsing file /opt/CPsuite-R80.40/fw1/amw/ioc/cur/md5/av_hash_ioc.eng`  
  `
  [DATE TIME] malware_parser_parse: Failed to parse file (/opt/CPsuite-R80.40/fw1/amw/ioc/cur/md5/av_hash_ioc.eng) - failed to open file (errno No such file or directory)`  
  `
  [DATE TIME] malware_parser_parse_included_file: malware_parser_parse() failed, file_name /opt/CPsuite-R80.40/fw1/amw/ioc/cur/md5/av_hash_ioc.eng`

* One or more path's in *"$FWDIR/conf/av_hash.eng"* points to *"/opt/CPsuite-R80.40/fw1/amw/ioc/cur/md5/...."*

* Another possible symptom: Policy installation fails with error code 0-2000174 or 0-3-2000174 or 1-3-2000174, $FWDIR/state/__tmp/FW1/install_policy_report.txt contains the following line: cmi_loader: 'signatures_done_cb' failed for app: (FILE_SECURITY), app_id (12)

## Cause

On the installation, the Gateway's directory: *$FWDIR/amw/ioc/cur/**md5/***   
has changed to: *$FWDIR/amw/ioc/cur/**hash/***   

"*$FWDIR/conf/av_hash.eng*" has not changed to reflect this.

## Solution

This problem was fixed. The fix is included in:

* [Check Point R81.10](https://support.checkpoint.com/results/sk/sk170416)
* [Jumbo Hotfix Accumulator for R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk170114) starting from Take 34
* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 119
* [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 237

<br />

If you choose not to upgrade, change the relevant paths in *$FWDIR/conf/av_hash.eng* file:
`#AV_hash DB`  

`$include ../amw_kss/update/cur/av_hash_small.eng`  
`$include ../amw/ioc/cur/md5/av_hash_ioc.eng`  
`$include ../amw/ext_ioc/cur/md5/av_hash_ioc.eng`  
`$include av_hash_prm.eng`  

To:
`#AV_hash DB`  

`$include ../amw_kss/update/cur/av_hash_small.eng`  
`$include ../amw/ioc/cur/hash/av_hash_ioc.eng`  
`$include ../amw/ext_ioc/cur/hash/av_hash_ioc.eng`  
`$include av_hash_prm.eng`  

In some cases, there may be more then 1 path pointing to the older "md5" path.  

Note:  
The same issue may still occur even if the fixed JHF Take is installed.  
In some cases --- for example, after upgrading from Traditional Anti-Virus to R81.10 or higher --- legacy objects or database remnants may cause the behavior to reappear.  
In such situations, apply the same workaround described in sk173248, by editing the $FWDIR/conf/av_hash.eng file to point to "hash" instead of "md5".

---

# 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