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"

Error: "The Host Module HTTPS port number specified is already in use." when installing WithSecure Policy Manager Server

Issue:

When installing WithSecure Policy Manager Server or Policy Manager Proxy the user receives the following error after clicking Next on the Configure ports page:

Error: "The Host Module HTTPS port number specified is already in use."

Resolution:

If the port you have chosen for WithSecure Policy Manager Server or Policy Manager Proxy communication is in use by other services (e.g Microsoft webserver), thus causing a conflict, you can solve the issue by changing the port Policy Manager Server will use or by deactivating the service causing the conflict or changing the port that service is using.

Policy Manager Proxy Upgrade
The error could be caused if clients are currently accessing the Policy Manager Proxy. If you are performing an upgrade of Policy Manager Proxy, you can stop all Policy Manager Proxy services and try the upgrade again, then it should work and the upgrade will be completed.

Article no: 000018483