Reference Number |
Related Article |
Found in ENSSP Version |
Resolved in ENSSP Version |
Issue Description |
DYN-717 |
|
2.0.0 |
2.4.0 |
Issue 1: Standalone installation of ENS Storage Protection doesn't preserve client settings on version migration.
Workaround: Configure the Storage Protection client settings manually from the ENS Console UI.
Issue 2: For ePO deployment on managed systems, when the NetApp policy option "Administrator account common to all filers" is unchecked, the required credentials for connection and scanning is wiped out after upgrade/deployment.
Workaround: Configure the "Default Administrator Account" settings manually from the ENS Console UI.
Resolution: This issue is resolved in ENSSP 2.4.0.
|
DYN-715 |
|
2.2.0 |
2.3.0 |
Issue: ENS Storage upgrade from 2.2 to 2.3 can prompt the user for a reboot due to Vscore dependency.
NOTE: According to MPT, a mandatory reboot is needed only if the customer encounters this issue (upgrade from 22.4 to 22.7 in an environment where EDR has hooked processes).
Workaround: Force reboot the system:
The customer can select ENS Platform security (10.7.0.5162.1) and TP (10.7.0.5200.1) as modules in the ePO deployment task followed by Storage Protection 2.3.0.639.1 in ePO to force reboot the system instead of selecting only Storage Protection.
|
DYN-681 |
|
2.1.0 |
2.3.0 |
Issue: The NetApp Scan Summary shows 0 due to a permission error.
Resolution: This issue is resolved in ENSSP 2.3.0. |
DYN-660 |
|
2.2.0 |
|
Issue: Queries and Dashboards aren't visible for non-administrator accounts in MVISION ePO (doesn't affect on-premises ePO). |
DYN-630 |
|
2.1.0 |
2.4.0 |
Issue: The NetApp Filer reports a random error event:
User not configured in any of the Vserver active scanner pools
Resolution: This issue is resolved in ENSSP 2.4.0. |
DYN-619 |
KB95613 |
2.1.0 |
2.2.0 |
Issue: ENSSP default queries and dashboards don't show threat events in results.
Workaround: We've provided updated custom queries and dashboards that you can import.
Resolution: This issue is resolved in ENSSP 2.2.0. See the related article for more information. |
DYN-618 |
|
2.1.0 |
2.2.0 |
Issue: A file isn't scanned due to a timeout when the NetApp credentials are enforced from Federal Information Processing Standard (FIPS)-enabled ePO.
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-604 |
|
2.0.0 |
2.2.0 |
Issue: The wrong name and description is shown in "Queries & Reports." A query for ENSSP is shown as "VSES130 Performance." The description is shown as "Retrieves information from VirusScan Enterprise for Storage of the scan server's performance."
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-601 |
|
2.0.0 |
2.2.0 |
Issue: The ePO query "Others: VSES130 Performance" shows the wrong product code "VSESTOMD1300."
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-605 |
|
2.0.0 |
2.2.0
or
ENS 10.7.0 February 2022 Update clean installation and ENSSP 2.1.0 |
Issue: The ICAPStats_Activity.log is missing a header.
Resolution: This issue is resolved in ENSSP 2.2.0. This issue is also resolved with an ENS 10.7.0 February 2022 Update clean installation and ENSSP 2.1.0. |
DYN-591 |
|
2.1.0 |
2.2.0 |
Issue: The Action column is empty for Storage in the UI Event Log.
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-531 |
|
2.1.0 |
2.2.0 |
Issue: The ENS Storage Protection extension is showing the Module as VSESTOMD1300.
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-412 |
|
2.0.0 |
2.1.0 |
Issue: File name path exclusions don't work on ENSSP.
Resolution: This issue is resolved in ENSSP 2.1.0. |
ENSW-114161 |
KB94949 |
2.0.0 |
ENS 10.7.0 November 2021 Update |
Issue: The ePO roll up data task fails with the following error:
invalid column name 'IsSTPClientDebugLoggingEnabled'
Resolution: This issue is resolved in the ENS 10.7.0 November 2021 Update. See the related article for more information. |
DYN-526 |
|
2.0.0 |
2.2.0 |
Issue: For specific types of potentially unwanted program samples, mfedsp.exe gets restarted. Hence, the statistic count is reset as 0, and the user interface isn't updated.
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-516 |
|
2.0.0 |
2.2.0 |
Issue: The View In Event Log link on the Quarantine tab doesn't redirect to the Event Log tab.
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-502 |
KB94881 |
2.0.0 |
|
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 UTF-16 LE BOM log file is generated.
See the related article for more information.
|
DYN-480 |
|
2.0.0 |
2.2.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
Resolution: This issue is resolved in ENSSP 2.2.0. |
DYN-543 |
|
2.0.0 |
2.1.0 |
Issue: ENSSP doesn't authenticate to the filer in NetApp ONTAP 7-Mode (8.x and 9.x versions).
Resolution: This issue is resolved in ENSSP 2.1.0. |