To raise the MaxExtractSize in SPE 8.2.1 and higher, use the following xmlmodifier command. A value of 100 configures SPE to use the default extract size of 100MB.
xmlmodifier -s //filtering/Container/MaxExtractSize/@value <value> filtering.xml
* 0 to 30719(in Mega Bytes)
Default value: 100
How do I confirm the current setting?
- Navigate to the default install folder of SPE, then do one of the following:
1. Use xmlmodifier to query the value:
./xmlmodifer -q //filtering/Container/MaxExtractSize/@value filtering.xml
2. Use bash grep to search for MaxExtractSize in filtering.xml:
grep "MaxExtractSize" filtering.xml
3. Use cmd find to search for MaxExtractSize in filtering.xml:
find "MaxExtractSize" filtering. xml
How do I know what value to adjust the MaxExtractSize to?
If the default value is insufficient to prevent SPE from recording a container violation for the sample file, then increase the value and re-scan.
A value higher than 100 will increase the extract size above the default value.
A value less than 100 would effectively lower the maximum permitted size of the extracted contents of a container file below the default value and is not recommended. It is likely to significantly increase the number of container policy errors in the SPE logs.
To understand the risk of setting a MaxExtractSize too high, please see the Additional Information section below.
To identify the value needed to scan a particular file
- To use the ssecls test scan tool to scan the file
ssecls.exe -mode scan -onerror leave -details -verbose "filename.ext"
- If an error occurs, check today's <SPE Install folder>/log/SSEYYYYMMDD.log file for the most recent log entry for the filename. If the log entry is "Container violation" (or "|4|2|3|3|" in the raw logs) , then double the MaxExtractSize and scan again. Return to step 1.
- If ssecls reports the file scanned without errors, or a different error occurs in the .log file, then the new value should be halfway between the value you tested and the previous value. Return to step 1.
- If you get to a point where the difference between your current test value and your previous test value is "1", you identified the borderline where container violation occurs for the sample file. The larger of these two values is the one which will permit the file without SPE logging container violation. You may still encounter other configurable limits.
- If the file is a .xlsx file. You can rename it to .zip. Unzip the file and get the file size.