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

# sk179591 - After running the "vsx_util upgrade" command, the version on the Virtual System is not the new version, and the policy fails because of version mismatch

| Property | Value |
|----------|-------|
| Solution ID | sk179591 |
| Date Created | 2022-06-26 |
| Last Modified | 2026-07-26 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82, R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * When you run the *sp_upgrade* script on Scalable Platforms, it fails when fetching the policy for one or more Virtual Systems (VSs).

* Policy fetch debugs show that the policy version does not align with the running version on the Security Gateway, meaning the policy was not compiled on the new version.

* On the Security Management Server, the `vsx_util upgrade` or `vsx_util downgrade` commands may complete with no errors.

## Cause

The `vsx_util` command failed to recompile the policy on the new version.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 79
* [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 77
* [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 180

If you choose not to upgrade, follow these steps.  

### Policy Failure

If the `vsx_util upgrade` or `vsx_util downgrade` commands complete with these errors:

* *Policy compilation failed*
* *Validating policy failed*

1. Change the VSX Gateway version to the previous version with the `vsx_util` command and then do the change on the desired version again.  

2. If step # 1 does not work, or takes too much time because of the environment dimension, then manually compile the policy for the applicable VS with the API.  
   `# mgmt_cli [-d <domain name>] --format json install-policy policy-package <policy name> --sync false targets <Virtual System object name> prepare-only true`  

3. If step # 2 does not fix the issue, [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) for assistance.   

### Database Failure

If the `vsx_util upgrade` or `vsx_util downgrade` commands complete with these errors:

* *Internal error: failed to save database*
* *Validating database failed*

Change the VSX Gateway version to the previous version with the `vsx_util` command and then do the change on the desired version again. If this does not work, [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) for assistance.

### Related Solution

* [sk158232 - "Upgrade operation failed for \[VS Name\]" error when 'vsx_util upgrade' fails for one or more Virtual Systems](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk158232)

---

# 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