Unable to check in the ZIP package to the ePO repository

Technical Articles ID: KB90036
Last Modified: 3/21/2022

Environment

McAfee Active Response (MAR) - all supported versions
McAfee Data Exchange Layer (DXL) - all supported versions
McAfee Data Loss Prevention (DLP) Endpoint 11.5 or later
McAfee Endpoint Security (ENS) 10.5.3 or later
McAfee Endpoint Upgrade Assistant (EUA) - all supported versions
McAfee ePolicy Orchestrator (ePO) 5.x
McAfee Threat Intelligence Exchange (TIE) Server 3.x

Problem 1

You can't check in the ZIP package to the ePO repository for the products that are listed in the Environment section.

The ePO console shows the following message:

The uploaded content exceeded the maximum size allowed.

The Orion.log file shows the following error:

Exception thrown by ActionBean:
com.mcafee.orion.core.servlet.SizeLimitExceededException: org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (282533025) exceeds the configured maximum (262144000)

Problem 2

You create an ePO deployable package using the EUA Package Creator, and select the ENS 10.5.3 or later standalone installation package. When you try to check the ZIP package into the ePO Master Repository, the operation fails and you receive the following error:

ERR_CONNECTION_RESET

After you refresh the page, you receive the following error:

You are not authorized for this operation

The Orion.log file might show an error message similar to the following:

ERROR [http-nio-8443-exec-104] servlet.ControllerServlet - Exception thrown by ActionBean:
com.mcafee.orion.core.servlet.SizeLimitExceededException: org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (299835620) exceeds the configured maximum (262144000)

Caused by: org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (299835620) exceeds the configured maximum (262144000)

Cause

The product ZIP package size is larger than the default size limit defined by the File.upload.limit entry in the epo.properties file.

ePO has two settings that limit the maximum size of product packages being checked in to the ePO Master Repository:

File	Orion.properties File location: <ePO installation folder>\Server\conf\orion\
Check-in method	Check-ins executed using ePO remote commands.
Setting	Orion.upload.max.size=######### Where ######### is the size in bytes
Default limit	268,435,456 bytes, which equal 256 MB

File	epo.properties File location: <ePO installation folder>\Server\conf\epo\
Check-in method	Check-ins executed using the ePO console.
Setting	file.upload.limit = ### Where ### is the size in megabytes
Default limit	250 MB

The following information is applicable only to remote commands:

For example, a customer has followed the advice in the MAR installation guide. The "Increase the McAfee ePO maximum upload size before installing the Active Response server" section suggests increasing the size of the orion.properties file to successfully upload the MAR packages. When a customer implements this advice using the ePO console, the package check-in fails with the same error message that is recorded in Orion.log file.
If you must increase the size limit specified in the relevant file, the suggestion is to increase the limit to 1024 MB.

NOTE: ePO 5.10.0 and later has a limit of 1 gigabyte.

IMPORTANT:

The default limit must match the limit defined in the epo.properties file entry line that reads file.upload.limit.
The most restrictive default limit is the value set in the epo.properties file. The default limit is set at 250 MB.
The limit depends on the check-in method.
If you change either setting limit, the suggestion is to change both so they match each other.
You must restart the ePO services after you change the limit.

Solution

Edit the epo.properties file and change the File.upload.limit size to 1024:

Locate the epo.properties file. File location: <ePO installation folder>\Server\conf\epo\
Right mouse click the epo.properties file, and select edit with Notepad.
Change the File.upload.limit size to 1024.
Save the file.
Restart the ePO services:
1. Press Windows+R, type services.msc, and click OK.
2. Right-click the following services and select Restart:
  
  McAfee ePolicy Orchestrator x.x.x Application Server
  McAfee ePolicy Orchestrator x.x.x Server
  McAfee ePolicy Orchestrator x.x.x Event Parser
3. Close the services window.
Check in the product package.

Related Information

NOTE: Content from KB90723 and KB90499 has been integrated into this article and unpublished.

Affected Products

Data Exchange Layer 6.x
Data Exchange Layer 5.x
Data Loss Prevention Endpoint 11.5.x (EOL)
Endpoint Security Firewall 10.7.x
Endpoint Security Firewall 10.6.x
Endpoint Security Threat Prevention 10.7.x
Endpoint Security Threat Prevention 10.6.x
Endpoint Security Web Control 10.7.x
Endpoint Security Web Control 10.6.x
Endpoint Upgrade Assistant All versions
ePolicy Orchestrator 5.10.x
Install/Uninstall
McAfee Active Response 2.x
Threat Intelligence Exchange Server 3.x
Threat Intelligence Exchange Server 2.3.x
Threat Intelligence Exchange Server 2.2.x
Upgrade/Migrate

Languages:

This article is available in the following languages:

English United States
Spanish Spain
French
Italian
Japanese
Portuguese Brasileiro
Chinese Simplified

Knowledge Center

Unable to check in the ZIP package to the ePO repository

Environment

Problem 1

Problem 2

Cause

Solution

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

Unable to check in the ZIP package to the ePO repository

Environment

Problem 1

Problem 2

Cause

Solution

Related Information

Affected Products

Languages:

Choose your region

Title

Title