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

# sk116221 - "Installation failed. Reason: Load on Module failed - failed to load Security Policy" error when installing Access Policy on Security Gateway R77.30 and lower with enabled Identity Awareness blade after the Management Server was upgraded to R80

| Property | Value |
|----------|-------|
| Solution ID | sk116221 |
| Date Created | 2017-03-06 |
| Last Modified | 2021-01-18 |
| Technical Level | General |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82.x, R82.20, R82.x, R81.20, R82, R82.20 |

## Symptoms

- "`Installation failed. Reason: Load on Module failed - failed to load Security Policy`" error in the following scenario:

1. Management Server was upgraded to R80
2. Installing Access Policy on Security Gateway R77.30 and lower
3. Identity Awareness blade is enabled on the involved Security Gateway

## Cause

Database corruption

## Solution

This problem was fixed. The fix is included in:

* [Check Point R80.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk111841)

On R80 Management Server, follow these steps:

1. Connect to the command line on the R80 Security Management Server / Multi-Domain Security Management Server.

2. Log in to the Expert mode.

3. On Multi-Domain Security Management Server, switch to the context of the relevant Domain Management Server:

   **`[Expert@HostName:0]# mdsenv <Name or IP address of Domain Management Server>`**
4. Go to the *$FWDIR/conf/* directory:

   **`[Expert@HostName:0]# cd $FWDIR/conf/`**
5. Run the following relevant command(s):

   * For Mail Server:

     `grep -e $'^\t\t: (' objects_5_0.C -e "is_mail_server (false)" -e mail_server_prop | grep -v "mail_server_prop ()" | grep mail_server_prop -B 2 | grep ":is_mail_server (false)" -B 1 | grep -e $'^\t\t: ('`
   * For DNS Server:

     `grep -e $'^\t\t: (' objects_5_0.C -e "is_dns_server (false)" -e -dns_server_prop | grep -v "dns_server_prop ()" | grep dns_server_prop -B 2 | grep ":is_dns_server (false)" -B 1 | grep -e $'^\t\t: ('`
   * For Web Server:

     `grep -e $'^\t\t: (' objects_5_0.C -e "is_web_server (false)" -e web_server_prop | grep -v "web_server_prop ()" | grep web_server_prop -B 2 | grep ":is_web_server (false)" -B 1 | grep -e $'^\t\t: ('`
6. If any of these commands returns a result, then perform the following:

   1. Open the host object that reported the problem (refer to the result of the commands above)
   2. In the '**`Servers`** ' section, ***check*** all options and close the window.
   3. Publish the session (do NOT install any policy yet).
   4. Open that host object again.
   5. In the '**`Servers`** ' section, ***clear*** all options and close the window.
   6. Publish the session.
   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