#11 Lessons Learned for Windows Install

[Marc Bernard]

After many struggles, I finally managed to get it to work... My config

• Windows Server 2016 Datacenter - 64-bit - V1607 - OS-build 14393.3564
• ClamAV-0.102.3.exe
  (from https://www.clamav.net/downloads#otherversions)
• ClamSAP: ClamAV to SAP NW-VSI Adapter Version: 0.101.6.0
  (from https://sourceforge.net/p/clamsap/bugs/8/, last attachment)

Here's the process that worked for me:

Windows:

• Install ClamAV
• Default installation went into C:\Program Files\ClamAV. However, it seems that space in the path causes problems.
• Move the complete C:\Program Files\ClamAV folder to C:\ClamAV
• Unzip ClamSAP files into C:\ClamAV folder
• Create file clamsap.reg as follows and merge to registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\ClamAV]
"ConfDir"="C:\ClamAV"
"DataDir"="C:\ClamAV\database"

[HKEY_LOCAL_MACHINE\SOFTWARE\ClamAV\ConfDir]
@="C:\ClamAV"

[HKEY_LOCAL_MACHINE\SOFTWARE\ClamAV\DataDir]
@="C:\ClamAV\database"

SAP System:

• Get program ZVSISETUP from https://github.com/strehle/abap_vsi_setup and implement it in SE38
• Run ZVSISETUP and set the adapter path to C:\ClamAV\clamsap.dll
• Start the scan provider in transaction VSCAN
• Implement and run the attached ZVSI_TEST program. It should end with "EICAR test virus found".

Troubleshooting:

If you get error "EICAR test virus not found, Scan error 13:ClamAV engine with internal,unknown error.", the reason is probably that another real-time virus check like Windows Defender is running on the server. Windows Defender will remove the temporary file to be scanned by ClamAV immediately which leads to an internal error in ClamAV and a failure in the SAP program.

Solution: Go to Windows Settings > Windows Defender > Add an exclusion > Exclude the folder for temporary files i.e. <drive>:\usr\sap\<sid>\tmp.</sid></drive>

Hope this helps some others,
Marc