# CPView and 'cpstat' command show different Application Control database versions

**Product**: Application Control  
**Version**: R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20  
**OS**: Gaia  
**Last Modified**: 2024-06-05

## Symptoms

- CPView > `Software-blades` tab > `Overview` page > the row `Application Control` > the column `Last update Number` shows the database version in the format "`DDMMYY_n`" (where "`n`" is a digit).

Example for the update from 09 July 2022:

```
CPVIEW.Software-blades.Overview
|-------------------------------------------------------------------------------------
| Overview SysInfo Network CPU I/O Software-blades Hardware-Health Management Advanced
|-------------------------------------------------------------------------------------
| Overview VPN SSL-Inspection IDA DLP Threat-Prevention Threat-Emulation Advanced ...
|-------------------------------------------------------------------------------------
| Updates Information:
|
|                     Blade status   Last update Number  Update Time
| Application Control enabled        090722_1            09Jul2022 17:42:50
| Anti-Virus          disabled       N/A                 N/A
| Anti-Bot            disabled       N/A                 N/A
| IPS                 disabled       N/A                 N/A
```

- The output of the "`cpstat appi -f update_status`" command shows the "`DB Version`" value in the format "`DDMMYYnn`" (where "`nn`" are two digits).

Example for the update from 09 July 2022:

```
[Expert@MyGw:0]# cpstat appi -f update_status

Update status:           up-to-date
Update description:      Gateway is up to date. Database version: 09072201.
Next update description: The next update will be run as scheduled.
DB version:              09072201

[Expert@MyGw:0]#
```

## Cause

It is the same information, just displayed in a different format.

- The CPView tool reads the Application Control Database Version value from the **$FWDIR/appi/update/Version** file.
- The "`cpstat appi -f update_status`" command reads the Application Control Database Version value from the **$FWDIR/appi/update/appi_status.C** file.

## Solution

This cosmetic problem was fixed. The fix is included starting from:

- [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 43
- [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 131
- [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 99
- [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 211

Check Point recommends to always upgrade to the [Recommended version](https://support.checkpoint.com/results/sk/sk95746) ( [Security Gateway](https://support.checkpoint.com/product/73) / [VSX](https://support.checkpoint.com/product/359)).

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties

**Access Level**: General  
**Status**: Approved by TAC  
**Date Created**: 2023-07-24  
**Last Modified**: 2024-06-05