Suppressing a scan error in Symantec Protection Engine for a file greater than 2 GB in size
Last Updated June 06, 2017
By design, there is a file size limit of 2 GB that is submitted for scanning. Therefore, SPE returns scan errors for the files of size greater than 2 GB, irrespective of whether the file is a plain file, a container file, or a file embedded inside a container file.
In such cases ICAP RESULT 500 “Internal Server Error” will be returned by Symantec Protection Engine to its client.
In order to suppress the scan errors in such scenarios, a new value called "BypassAVScanning" is created in the category3.xml file.
Converted readable format below:
Thu May 25 10:07:51 India Standard Time 2017, The Symantec Protection Engine has encountered a scan error, Event Severity Level = Error, Scanner = AntiVirus, Result ID = 30, URL = icheck.symantec.com/prav.tar, File name = prav.tar, Client IP = 10.219.212.21, Scan Duration (sec) = 3.401, Connect Duration (sec) = 432.700, Symantec Protection Engine IP address = 10.219.209.97, Symantec Protection Engine Port number = 1344, Uptime (in seconds) = 1298
Perform the following steps to deploy this file:
Download category3.xml from this document.
Stop SPE service.
Copy and paste category3.xml to <Drive>\Program Files <x86>\Symantec\Scan Engine.
Start SPE service.
Note: There is a version number <custom version="070503"> that must match the installed version number. For Protection Engine Version 7.5.3 it needs to be <custom version="070503">. For Symantec Protection Engine 7.8.0 it would need to be <custom version="070800">. For Symantec Protection Engine 7.9.0 it would need to be <custom version="070900">. This can be updated using a text editor like NotePad.
Tip: For steps on configuring Symantec Protection Engine to scan large files, see Related Articles in the right navigation.
After you make this configuration, if ICAP Scan request contains ALLOW ICAP header, SPE responds with ICAP 204 NO CONTENT NECESSARY. Otherwise, SPE responds with ICAP 200 OK.