Updated issue ENSW-114161 in the "Non-critical known issues" section as resolved in ENS 10.7.0 November 2021 Update.
November 8, 2021
Added issue DYN-542 to the "Critical known issues" section.
October 15, 2021
Added issue DYN-412 to the "Non-critical known issues" section.
October 7, 2021
Added issue DYN-543 to the "Non-critical known issues" section.
September 30, 2021
Added issue ENSW-114161 to the "Non-critical known issues" section.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Contents
Click to expand the section you want to view:
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
Issue: The event logs show the following error. This issue occurs due to the implementation in ENSSP for the Windows predefined variable "MAX_PATH". When a scan triggers when copying a file from the filer, if the file path length is longer than 260 characters, it causes mfedsp.exe to crash.
The mfedsp MMS Service terminated unexpectedly
Workaround: Reduce the file paths to fewer than 260 characters to avoid the issue and mfedsp.exe terminating.
Reference Number
Related Article
Found in ENSSP Version
Resolved in ENSSP Version
Issue Description
DYN-412
2.0.0
Issue: When you exclude a path including "\\?\" in the ENS console, it fails to save with the following message. But, you can set the exclusion in the ENSSP policy in ePO.
Enter a valid pattern
Workaround: Use wildcards instead of "\\?\" for the exclusion. Example: **\<uncpath>\**
Issue: The ePO roll up data task fails with the following error:
invalid column name 'IsSTPClientDebugLoggingEnabled'
Resolution: This issue is resolved in ENS 10.7.0 November 2021 Update. See the related article for more information.
DYN-526
2.0.0
Issue: For specific types of potentially unwanted program samples, mfedsp.exe gets restarted. Hence, statistic count is reset as 0, and the user interface isn't updated.
DYN-516
2.0.0
Issue: The View In Event Log link on the Quarantine tab doesn’t redirect to the Event Log tab.
Issue: The log file format under Reports, Log Files, Log File Format is reflected in the user interface. But, files with an incorrect format are generated in a log location for ICAP / NetApp Scan Activity logs.
For the ANSI log format, a UTF-8 log file is generated.
For the UTF-8 log format, a UTF-8 BOM log file is generated.
For the UTF-16 log format, a UC2-LE BOM log file is generated.
See the related article for more information.
DYN-480
2.0.0
Issue: When ENSSP performs ICAP scanning on a malicious file with the clean/continue action, the action taken after the scan doesn't display in the ICAP Scan Activity log. Also, if the file is located inside a ZIP file, some %s are appended to the log message. For example, for a ZIP with EICAR, the ICAP Scan Activity log shows:
Scan Result File from filer %s scanned : %s EICAR test fileScan Result File from filer %s scanned : %s
DYN-543
2.0.0
Issue: ENSSP doesn't authenticate to the filer in NetApp ONTAP 7-Mode (8.x and 9.x versions).
NOTE: Any future product functionality or releases mentioned in the Knowledge Base are intended to outline our general product direction and should not be relied on, either as a commitment, or when making a purchasing decision.
