Anti-Malware scan failures and cancellations
Anti-Malware scans can fail or be cancelled for several reasons, which have different recommended actions.
This topic includes:
These events can occur for manual, quick, or scheduled scans.
Anti-Malware scan failure events
This table provides possible reasons for system events 793, 795, and 1543 (Malware Scan Failure).
Event reason | Reason ID * | Description | Recommended action |
---|---|---|---|
Empty configuration | 31 | Malware Scan could not be started. This is caused by an empty Malware Scan configuration. |
|
Anti-Malware module is off | 30 | Malware Scan could not be started. This is because the Anti-Malware module is turned off. |
|
Anti-Malware service stops | 7 | Malware Scan failed because the Anti-Malware service is being terminated. |
|
Anti-Malware engine is offline | 9 | Malware Scan failed because the Anti-Malware engine is offline. |
|
Fail to access configuration | -2 | Malware Scan failed because of an inaccessible Anti-Malware configuration. (This may be due to an unexpected internal error or timing issue.) |
|
Other scan task is running | -16 | Malware Scan failed because another scan task is in progress. (This may be due to an unexpected internal error or timing issue.) |
|
Unknown reason on agent | 10 | Malware Scan failed for an unknown reason. |
|
* The reason ID is included in events forwarded to an external Syslog, SIEM server, or to Amazon SNS. It is not displayed in Deep Security Manager.
Anti-Malware scan cancellation events
This table provides possible reasons for system events 1526, 1528, and 1540 (Malware Scan Cancellation Completed).
Event reason | Reason ID * | Description | Recommended action |
---|---|---|---|
Cancel by user | 1 | Anti-Malware scan was canceled manually. | Run the scan again. |
Server reboot | 32 | Anti-Malware scan was canceled, possibly because the computer being scanned was shut down or restarted. |
Check that the computer is on and run the scan again. |
Anti-Malware service restart | 7 | Anti-Malware scan was cancelled because the Anti-Malware service was being restarted. |
|
Deep Security Agent restart | 6 | Anti-Malware scan was cancelled because the agent was being restarted. Check that the Anti-Malware module is online and run the scan again. |
Also make sure there is no agent upgrade or policy change taking place during scanning because these tasks may cause the agent to restart. |
Unknown reason | -1 | Anti-Malware scan was cancelled for an unknown reason. |
|
* The reason ID is included in events forwarded to an external Syslog, SIEM server, or to Amazon SNS. It is not displayed in Deep Security Manager.