Product Troubleshooting WithSecure Business Suite

Warning message of "This installer version is going to be obsoleted at the end of year 2024" during the installation of Linux Security 64
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Updating malware definitions on an isolated client using fsaua-update_32.exe fails with message ERROR:Update archive file is broken
Where can I find the key code for the latest version of my Business Suite software?
Error: "The keycode that you entered is not valid" when trying to export an installation package for Client Security or Server Security
"capricorn-linux64" channel are added in product's database after Linux Security 64 update version 12.0.482 and Atlant update version 1.0.319
How to schedule Business Suite Software Updater to install updates automatically to Client Security and Server Security devices?
f-secure-baseguard services gone for Linux Security 64 and Atlant after FSBG 1.0.907 update
How to hide the real-time scanning exclusions or other exclusions from users in the local Client Security or Server Security user interface?
WithSecure Client Security or Server Security Web content control is not blocking categories that are set as "Disallowed"

Warning 'EcProcessVirusScanQueueItem' during virus scanning

Warning 'EcProcessVirusScanQueueItem' during virus scanning

Symptoms

The user is displayed the following warning during virus scanning:

EcProcessVirusScanQueueItem

Diagnosis

The user receives the below error on a regular basis on his Microsoft Exchange 2007 Server with SP1. The user has F-Secure Anti-Virus for Microsoft Exchange installed but not F-Secure for File Servers.

Error message:

Unexpected error 0x8004010f occurred in "EcProcessVirusScanQueueItem" during virus scanning. Mailbox Database: /o=XXX LLP/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=LFEX1/cn=Microsoft Private MDB Folder ID: a-1A6A4F2F Message ID: 1-1093784CC

Solution

This is a Microsoft issue which can occur on a Microsoft Exchange Server running any antivirus program which integrates with Microsoft Exchange.

As this issue is not caused by F-Secure Anti-Virus for MS Exchange, contact Microsoft to resolve this issue.