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

# sk146955 - "Failed to Load Security Policy: No such file or directory  Fetching Security Policy Failed" error when running 'vsx_util reconfigure'

| Property | Value |
|----------|-------|
| Solution ID | sk146955 |
| Date Created | 2019-02-25 |
| Last Modified | 2019-03-28 |
| Technical Level | Advanced |
| Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20, R82.10, R81.20, R82 |
| OS | Gaia |

## Symptoms

- * 'vsx_util reconfigure' command fails on device at stage 6 (Policy Install) with the following error:  
  `"Failed to Load Security Policy: No such file or directory`  
  `
  Fetching Security Policy Failed"`  
* Similar logs are seen in Kernel debug (fw ctl debug -m fw + filter) output:  

  `[DATE TIME];[cpu_0];[fw4_0];fwioctl: CONFIG_PRELOAD_GETPOLICY: starting;`  
  `
  [DATE TIME];[cpu_0];[fw4_0];fwioctl: CONFIG_PRELOAD_GETPOLICY: before fwk_atomic_blade_get_curr_policy();`  
  `
  [DATE TIME];[cpu_0];[fw4_0];fwk_atomic_blade_get_curr_policy: cfg=e5341af4 type=malware;`  
  `
  [DATE TIME];[cpu_0];[fw4_0];fwk_atomic_blade_get_curr_policy:
  fw_mal_get_curr_policy() failed;`  
  `
  [DATE TIME];[cpu_0];[fw4_0];fwk_atomic_blade_get_curr_policy: done ret=1;`

## Cause

The Security Gateways settings were modified Prior the re-configure operation.

Instead of adding the bonds and routes manually, they were restored to the Security Gateway with OS backup/restore from an **active**VSX gateway.

Clarification regarding OS backup:

Utilizing an OS backup is **allowed**, however there are a few things to consider:

1. If the OS backup was taken when the module was **already VSX**, this backup is not usable for this procedure.

2. the backup may contain the Management interface and routes **ONLY** ! all other routes and interfaces must be configured **after** the reconfigure action.

3. The main Target is that a reconfigure needs to be done on a **non-VSX Gateway,** without interfaces and routes configuration except for the interface facing the Management server.

If for example there are a lot of bonds to configure and/or a few hotfixes to install \> to apply this we must use a backup from **before**the conversion to VSX.

However, if the backup is from a **working**state, where the Gateway is VSX \& it was reverted to Gateway state again, the reconfigure will fail as well, so this work around is not an option.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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