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

# sk182248 - Policy installation fails after on-boarding with IoT

| Property | Value |
|----------|-------|
| Solution ID | sk182248 |
| Date Created | 2024-04-25 |
| Last Modified | 2024-04-29 |
| Technical Level | Advanced |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R81.20, R81.20 |

## Symptoms

- * Policy installation fails after on-boarding with IoT with one of these error messages:

  "*ERROR: Duplicate keys \<08080808\> in table dns_server_rules"*

  "*ERROR: table dns_server_rules undefined"*

  "*ERROR: syntax error"*

  "*ERROR: unknown macro or function spii_record_conn_match"*

  "*ERROR: unknown macro or function RECORD_CONN_EX"*

  "*ERROR: unknown macro or function USER_PASS_CONNECTION_SCV"*

  "*ERROR: unknown macro or function USER_PASS_CONNECTION"*
* IoT agents are running on the Management Server and on the Security Gateway.

## Cause

IoT creates a new layer in the policy that creates new objects related to the IoT policy. For example, one of these objects is a host with the IP address 8.8.8.8. The customer already had one host with the name host_DNS_google. The IoT policy creates a new host called DNS_GOOGLE that has the same IP address 8.8.8.8.

As a result, there are duplicate objects with the same configuration.

## 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