Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Phuc138878
Explorer
Jump to solution

R81.10.17 Upgrade – Policy Installation Failed (Error 00351)

Dear Check Point Support Team,

We would like to request your assistance regarding an issue after OS upgrade.

1. Upgrade Information

We have upgraded the Security Gateway OS from:

  • Version: R81.10.08

  • To Version: R81.10.17 (Build R81.10.17_996004721)

The upgrade process was completed successfully without any interruption or error during installation.


2. Issue Description

After the upgrade, we are unable to install policies successfully.

The following issues are observed:

  • VPN policy cannot be installed

  • NAT policy cannot be applied

  • IPS policy cannot be applied

  • Some Security Settings policy changes could not be applied

  • Error message appears during policy installation

System Notification shows:

Error has occurred while applying the Firewall settings (error 00351).
If the problem persists, contact Check Point Technical Assistance Center.

From SmartConsole logs:

  • “VPN policy change could not be applied”

  • “IPS policy change could not be applied”

  • “NAT policy change could not be applied”

  • “A policy change could not be applied”

High Availability policy shows as applied successfully, but other policies are failing.

I just tried to restore the previous version, but there is still an error. 

May you give any advice about this case?

0 Kudos
1 Solution

Accepted Solutions
Phuc138878
Explorer

Thank you for the reference.

I have opened a TAC case with Check Point and worked with them on the issue. The root cause was identified as a custom URL object with no category configured.

View solution in original post

2 Replies
_Val_
Admin
Admin

Please look into https://support.checkpoint.com/results/sk/sk100610 and follow the troubleshooting steps for your version. If required, open a TAC call: https://help.checkpoint.com

Phuc138878
Explorer

Thank you for the reference.

I have opened a TAC case with Check Point and worked with them on the issue. The root cause was identified as a custom URL object with no category configured.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events