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

# sk117233 - "Failed to read record number 1" pop-up error message appears upon launching of SmartView Tracker 

| Property | Value |
|----------|-------|
| Solution ID | sk117233 |
| Date Created | 2017-05-07 |
| Last Modified | 2026-02-25 |
| Technical Level | General |
| Products | SmartConsole |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- "Failed to read record number 1" pop-up error message appears upon launching of SmartView Tracker.

## Cause

There are two probable reasons why this may occur:

* Log server has run out of disk space
* *fw.log* file has become corrupt

## Solution

* If the log server ran out of disk space, you can perhaps free disk space by deleting some old log file, and then run the *fw logswitch* command.
* If the log file is corrupt, running the *fw logswitch* command should resolve the SmartView Tracker error. Running *fw repairlog \<log file name.log\>* might repair the corrupted logs.

**Note: If you choose to attempt an *fw repairlog* on the *fw.log* file, you must first execute a *cpstop* or *mdsstop_customer \<CLM IP\>* on the log server before proceding.**

<br />

---

# 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