Loading...

Knowledge Center

ERROR: The transaction log for database 'ePO_DBNAME' is full due to 'ACTIVE_TRANSACTION' (ePolicy Orchestrator upgrade fails)
Technical Articles ID:   KB89461
Last Modified:  7/10/2018
Rated:

Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Problem

An ePO upgrade fails without a visible error. The upgrade then automatically rolls back to the previous ePO version.

NOTE: This issue can occur while upgrading between any 5.x.x builds.

The following messages are recorded in log files:

ePO5xx-error.ini:
 
[ErrorLog]
ErrorString=FAILURE: In LaunchApplication while trying to run the following program:
ActionName=Prod_InstallEpoCore
Task=Checking in epoST
"C:\Users\ADMINI~1\AppData\Local\Temp\2\McAfeeLogs\EPO530-Troubleshoot\OutputFiles\epoST.bat"
Return code: 1

This reference indicates you should check the file McAfeeLogs\EPO5xx-Troubleshoot\OutputFiles\epoST.bat.

epoST.bat:
This file indicates you should check the file name McAfeeLogs\EPO5xx-Troubleshoot\OutputFiles\epoST.err.

epoST.err:
 
BUILD FAILED
D:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\EPOCore\5.3.2.156\install.xml:337: The following error occurred while executing this line:
D:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\EPOCore\5.3.2.156\install.xml:462: The following error occurred while executing this line:
D:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\EPOCore\5.3.2.156\install.xml:136: java.sql.SQLException: The transaction log for database 'ePO_DBNAME' is full due to 'ACTIVE_TRANSACTION'.

This file records the BUILD FAILED error and includes information about where the upgrade was interrupted.

Cause

This issue occurs because the SQL database has reached the maximum allowed size. For SQL Server Express, the database may have reached the maximum allowed size. For full versions of SQL Server, the Auto Growth function is disabled or restricted.

Any ePO upgrade can cause the SQL database to grow. If the database is already full, or Auto Growth has been restricted, the upgrade will fail and ePO will roll back to the previous version.

The maximum database sizes for the various versions of SQL Express are:
  • SQL Server 2008 Express R2 - 10GB
  • SQL Server 2008 Express (without R2) - 4GB
  • SQL Server 2012 Express - 10GB

Solution

For SQL Server Express, reduce the size of the database before you re-attempt the upgrade.

For full versions of SQL Server, perform the following steps to enable Auto Growth for the MDF and LDF files:
  1. Launch SQL Server Management Studio.
  2. Select the ePO DB properties.
  3. Select Files.
  4. Select Database files.
  5. Under Auto Growth, click the option to make the following changes:

    Default criteria for the MDF file:
    • Enable Auto Growth
    • File Growth: In MegaBytes
    • Maximum File Size: Unrestricted File Growth.

    Default criteria for the LDF file:
    • Enable Auto Growth
    • File Growth: In Percentage [Default = 10]
    • Maximum File Size: Restricted File Growth (MB) = 2,097,152
       
  6. Exit SQL Server Management Studio and re-attempt the upgrade.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.