> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/auto-upgrade/troubleshooting-auto-upgrade/software-auto-upgrade-failed-due-to-open-reports-in-period.md).

# Software Auto-Upgrade Failed Due to Open Reports in Period

Some sites have experienced upgrade durations exceeding two hours, causing the process to time out and fail. The root cause is an excessive accumulation of unprocessed data in an open reporting period (Period 3 or 4), which forces the Auto Upgrade engine to restore a disproportionately large dataset before it can proceed. This is generally caused by sites failing to close reports for those periods.

Sites may encounter one of the following errors when attempting an Auto Upgrade:

* “**E9092** Software auto-upgrade failed due to open reports in Period-4”
* “**E9093** Software auto-upgrade failed due to open reports in Period-3”

The most likely cause is that the Roll Up DB Reports setting (found under Report > Report Configuration in the Configuration Client) defaults to YES for both Month and Year. This means that the Database (DB) from the Daily report rolls up into the Monthly report. The DB from the Monthly report rolls up to the Yearly report. Sites that do not use monthly (31-day) or yearly (365-day) reports may be unaware that these reports must be closed. Not closing these reports allows data to accumulate into large volumes.

## Solution

**Option A — Site Does Not Use Monthly or Yearly Period Reports (Recommended)**

If the site does not use the affected period reports, perform the following steps:

1. Log in to Config Client, hover over the Reporting menu, and select Report Configuration.
2. Select 3 – Month from the Period Configuration pull-down menu.
3. Set “Roll Up DB Reports” to NO.
4. Select 4 – Year from the Period Configuration pull-down menu.
5. Set “Roll Up DB Reports” to NO.
6. Save the configuration.
7. From the Point of Sale (POS), navigate to CSR Func, Maintenance Menu, and select Check For VRSD to re-stage the download.
8. Select Apply Upgrade to start the upgrade process again.

{% hint style="info" %}

* The Verifone Helpdesk may have to delete the existing download from the Commander and re-stage the upgrade on the server.
* After the upgrade completes, the site will not be able to recover the deleted period data.
  {% endhint %}

**Option B — Site Uses Period Reports**

If the site does use the affected period’s reports and wants to preserve the data, follow these steps:

1. From the POS, navigate to CSR Functions > Reporting Menu.
2. Select the Close YEARLY Report. This will start to close all period reports in sequence (Shift, Day, Month, Year).
3. After the Year closes, navigate to CSR Func, Maintenance Menu, and select Check For VRSD to re-stage the download.
4. Select Apply Upgrade to start the upgrade process again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/auto-upgrade/troubleshooting-auto-upgrade/software-auto-upgrade-failed-due-to-open-reports-in-period.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
