Administrator

Troubleshooting Virus Scan

Review solutions to common issues you may encounter when working with Virus Scan.

No log output after successful VSA configuration

Upon successful configuration of the VSA, when SAP Mobile Platform Server starts the NW-VSI, and successfully loads the VSA, normally, there are no Virus Scan service messages output to the server log, even when an infection is found. (Infections found will be output in the security_N.log file.)

To include information about the VSA and the scan engine being used, you will need to configure the SAP Mobile Platform Server log settings:
  1. In Management Cockpit, select Start of the navigation path Logs Next navigation step Log Settings End of the navigation path.
  2. For the Foundation component, select INFO as the log level.
  3. Click Save.
Server log output will output information about the VSA similar to the example below when the NW-VSI is successfully started and is active.
2014 03 07 12:03:23#+00#INFO#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###Found VSI Scan Provider VSA_DEFAULT |
2014 03 07 12:03:23#+00#INFO#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###VSA vendor: McAfee Engine Adapter for NW-VSI 1.00 |
2014 03 07 12:03:23#+00#INFO#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###VSA engine: 5.6.00 |
2014 03 07 12:03:23#+00#INFO#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###Engine date: Wed Jan 15 20:08:00 GMT 2014 |
2014 03 07 12:03:23#+00#INFO#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###VSI Virus Scan Service initialization was successful |

Virus Scan Initialization Exceptions

After you configure the VSA, if SAP Mobile Platform Server encounters issues when attempting to start the NW-VSI, a warning is output in the server log. Details about the exception which may help identify the problem are included. The following are common virus scan initialization exceptions and the corresponding messages output to the server log.
Exception and Potential Fix Log Message
Incorrect DLL - Ensure that you have the correct vsa.dll for your virus scan engine.
2014 03 07 11:48:08#+00#WARN#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-16###Cannot initialize Virus Scan Service. The following service exception occurred: Load of the VSA failed, might not correct version. |
2014 03 07 11:48:08#+00#WARN#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-16###No virus scan will be performed 
DLL Not Found -Ensure that you have extracted the dll to the correct location, and that you have configured the AdapterPath property to point to the correct location for your DLL.
2014 03 07 11:56:01#+00#WARN#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###Cannot initialize Virus Scan Service. The following service exception occurred: Can't load library: C:\unknown.dll |
2014 03 07 11:56:01#+00#WARN#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-17###No virus scan will be performed |
Invalid Parameter - Ensure that the PoolMaxInstances property for the VSA is set to a value greater than 0.
2014 03 25 12:28:33#0-400#WARN#com.sybase365.mobiliser.framework.vscan.scanner.impl.VScanImpl##anonymous#aims-init-13###Cannot initialize Virus Scan Service. The following service exception occurred: The adapter start failed with error: "VSI_E_INVALID_PARAM" |

Virus Found Exceptions

When the Virus Scan Service finds a virus in its scanning, a warning message similar to the example below is output into the security_N.log file:
Mar 7, 2014 12:11:53 PM ...y.core.util.SecurityAudit.VIRUS_FOUND [Thread[Thread-20,5,main]] Warning: Objectname: VSA_DEFAULT Reason: The virus "EICAR test file" was found in VSA_DEFAULT!