Support articles

Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.

Extended Detection and Response

View all

Collaboration Protection

  • Elements Collaboration Protection shows "Organization is not available Selected organization"

    Read more
    Issue:

    When trying to access a customer's company account in Elements Collaboration Protection portal as a reseller partner, it gives the error "Organization is not available Selected organization.....".

    Resolution:

    This error can happen due to browser cache issues, especially if you as a reseller partner were already logged in to the Elements Security Center when you sold the Collaboration Protection subscription through the Partner Portal and then try to immediately access the customer's Collaboration Protection product in the Elements Portal.

    If you receive the "Organization is not available Selected organization" error when trying to access a customer's Collaboration Protection organization in the Elements Security Center portal, try first to log out from the Elements Security Center portal, restart the browser and re-login to the portal.

    If issue persists, try clearing your browser cache or try to log in using an incognito or inprivate browser window.

    If clearing the cache or logging in with an incognito or inprivate browser window did not help, make sure from the Management > Organization Settings > Security administrators page that you have Collaboration Protection access rights.

  • Elements Collaboration Protection wrong amount of used licenses after turning protection off for one or more mailboxes

    Read more
    Issue:

    Elements Collaboration Protection shows wrong amount of used licenses after turning protection off for one or more mailboxes. The Elements Security Center portal's Management > Subscriptions page's Used column shows mailboxes count to be higher than there are protected mailboxes on the Cloud service's Exchange tab. 

    Resolution:

    The Elements Collaboration Protection license usage data that is shown on the Eleemnts portal's Management > Subscriptions page is actually a daily activity/usage and not the total amount of protected mailboxes.

    Therefore, it can change each day and is likely that the number in the Subscription view will occasionally be lower comparing to the amount of protected mailboxes. 

    We advise to go to the Elements portal's Collaboration Protection > Cloud Services > "Your Service" > Exchange tab and view the Available licenses count there. 

  • Is there a way to disable the email notification alerts for detections in Elements Collaboration Protection?

    Read more
    Issue:

    Is there a way to disable the email notification alerts for detections in Elements Collaboration Protection? Users would not want to receive the notification emails when malware has been found in an attachment or an email has been quarantined because it included a malicious URL address.

    Resolution:

    Yes, it is possible to disable the notifications that are sent to the users about detections by Elements Collaboration Protection:

    If you want to disable the user notifications for detection completely for when malware has been detected in an email:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > Malware
    5. Untick the Notify the user about detections with the following severities:
    6. Click Save

    If you want to disable the user notifications for detection completely for when malicious URL or suspicious URL has been detected in an email:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > URL scanning page
    5. Untick Notify the user about detections with the following severities under both Malicious URL and Suspicious URL
    6. Click Save

    If you want to disable the user notifications for detection completely for when a compromised account detection has been made towards the users email address:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the Exchange > Compromised accounts page
    5. Untick Notify the user about detections with the following severities
    6. Click Save

    If you only want to not send user notifications based on the severity of the alert:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Collaboration Protection > policies page
    3. Open the policy that is in use on your cloud service
    4. Go to the General > Notifications page
    5. From the User notifications based on severity, select the desired severity level that triggers a user notification:
      1. All (Low, Medium, High & Critical)
      2. Medium, High & Critical
      3. High & Critical
      4. Critical
    6. Click Save

Endpoint Detection and Response

  • Elements EDR Advanced response task shows "Failed" status

    Read more
    Issue:

    After creating an advanced response task for Elements Endpoint Detection and Response (EDR), the State is shown as Finished but the Progress column shows the task Failed.

    What can cause the advanced response task to fail? 

    Resolution:

    If the EDR advanced response tasks fail, first you need to make sure that the Advanced response actions are enabled in the Elements profile:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Profiles page
    3. Open the profile that is in use on the devices
    4. Go to the General settings page
    5. In the Integrations section, make sure that Advanced response is enabled
    6. Click Save profile

    Also make sure that the required network connections are allowed. For that you can run the wsconnectionchecker.exe tool found in the Elements Agent installation folder: C:\Program Files (x86)\F-Secure\PSB\ui

    The connection checker tool has tests for WithSecure EDR Response Server, which need to succeed for the advanced response actions to work. The addresses are also mentioned in the user guide: Turn on advanced response actions | Elements Endpoint Detection and Response | Latest | WithSecure User Guides 

    If response actions are enabled in the profile and the connections show OK status, but the response action tasks would still fail, you need to make sure that the task you have created does not have any errors. For example if you have created a retrieve files task, you need to make sure that the folder path is valid. 

  • How to install stand-alone Elements EDR without removing conflicting software?

    Read more
    Issue:

    I am installing standalone Elements Endpoint Detection and Response with the ElementsAgentInstaller.exe file, and it detects a 3rd party antivirus as a conflicting product during.

    How can I proceed with the Elements Agent installation without sidegrading or uninstalling the conflicting antivirus software?

    Resolution:

    The Elements Agent EXE installer contains sidegrade functionality, where it will detect 3rd party antivirus program as conflicting software and automatically try to uninstall it.

    If you do not wish to uninstall conflicting products when installing Elements Agent with a stand-alone Elements Endpoint Detection and Response (EDR) subscription key, you can use the command-line parameter --skip-sidegrade to turn off automatic uninstallation of the existing products:

    1. Open a Command Prompt with administrator privileges
    2. Navigate to the folder where you have saved the ElementsAgentInstaller.exe
    3. run command:
      1. ElementsAgentInstaller.exe --voucher aaaa-bbbb-cccc-dddd-eeee --language en --skip-sidegrade "*"

    This will skip the sidegrade on any conflicting products during installation. 

    More detailed information regarding the Elements Agent EXE installer's Command-line parameters can be found in the user guide: Command-line parameters | Elements Endpoint Protection | Latest | WithSecure User Guides

  • After installing Elements Agent client with EDR subscription, the message "Device sensor is not operational" show up

    Read more
    Issue:

    After installing Elements Agent client with EDR subscription, the message "Device sensor is not operational" is shown in the local Elements Agent user interface.

    Resolution:

    You need to ensure that you have allowed the network traffic to the following addresses in your network firewall. The client sensor silently collects activity from the endpoint on which it is installed and then submits a representation of this data to a backend.

    To guarantee proper transmission, the endpoints need to be able to communicate over HTTP and HTTPS, port 443 with the services listed here:
    https://community.withsecure.com/en/kb/articles/31217-network-addresses-for-withsecure-elements-cloud-managed-products

    You should also allow connections to the digicert.com domain, as the Windows API may need to verify WithSecure services that are signed with a certificate that is issued by Digicert.

    In case you have an SSL interceptor to intercept the network traffic, we recommend creating whitelisting on the SSL interceptor for the EDR addresses. EDR and Countercept use the same certificate pinning approach that prevents connectivity when TLS interception solutions are used.

    Services that need to be whitelisted in the interceptor are:

    • DIS
    • Doorman
    • FAMP/Response

     

    If the connectivity is OK on the device and you still receive the error "Device sensor is not operational", you can check if the EDR sensor has at all been installed:

    1. Right click the Elements Agent icon on the device
    2. Click "Check for updates" 
    3. Scroll down the "Update history" list and check if it includes an entry for WithSecure Sensor (64-bit) and that it shows status as "installed" 

    If the WithSecure Sensor is completely missing or status is not installed, then the sensor installation failure can be due to a device having had Elements MDR or WithSecure Countercept installed on it before and the MDR or Countercept installation hasn't been fully uninstalled. 

    Elements MDR and Countercept both have a similar WithSecure Sensor component and if it hasn't been uninstalled before installing Elements Agent, the installation of the Elements Agent version of the sensor will fail. 

    To solve the issue, you will need to run the WithSecure uninstallation tool to uninstall both Elements Agent and Elements MDR / Countercept. You need to restart the device after running the uninstallation tool, then you can try to install Elements Agent back to the device. 

     

     

    ---In case device has 3rd party agent type security---

    Example :MaLion Security Point (Intercom) 

    MaLion Security Point (Intercom) installs a Winsock LSP (MarFtpLsp.dll, pmilsp.dll). It is loaded into fshoster32.exe and breaks name resolution on the EDR sensor upload path (obusclient2 → fswinssl → WinSock). The sensor cannot submit data and is reported as disconnected.The Connectivity Tool uses WinHTTP, which does not go through the LSP the same way. A clean report therefore does not rule this issue out. Ruled out: product defect, licence, firewall or proxy, DNS or routing.

    How to confirm
    • fshoster32.exe process log shows MarFtpLsp.dll and pmilsp.dll loaded.
    • obus/client2.1.log shows Cannot resolve address and backing off.
    • ATP/submission.log shows continuous Unsuccessful submission and no Successful submission.
    Resolution
    1. Disable MaLion Security Point (do not just stop it) and reboot.
    2. Check that submission.log shows Successful submission and the backlog drains. The GUI can take up to about 1 hour to clear.
    3. Permanent fix: Have Intercom or the partner exempt the whole WithSecure installation folder in MaLion, not just fshoster32.exe. Other Elements Agent processes use the same path, and process names can change between versions.
    4. Check that the subscription is valid.

    Do not leave MaLion disabled permanently. 

Endpoint Protection

  • Software Updater reports GIMP updates for the product “GIMP 3+ (User)” as completed, but GIMP 2.xx remains installed on the system.

    Read more
    Issue:

    Software Updater reports multiple GIMP updates for the product “GIMP 3+ (User)” to version 3.x as completed in the WithSecure Elements portal, but GIMP 2.10 still remains installed on the local system.

    Checking the affected system

     

    • GIMP 2.10.38-1 installed machine-wide under C:\Program Files\GIMP 2.
    • GIMP 3+ (User) installed in the context of an individual Windows user.

    Therefore, a successful update of GIMP 3+ (User) does not replace or upgrade the machine-wide GIMP 2.10 installation. The older GIMP version can remain installed and continue to be detected on the endpoint.

    Note, that per-user applications also require an active interactive user session when Software Updater performs the installation. If no suitable user session exists, the installation can fail with: WAAPI_ERROR_NO_ACTIVE_USER_SESSION

     

    Why is GIMP not updated from version 2.x to 3.x?

    Note, that this issue can affect software installations/upgrades supported by Software Updater and not just GIMP.

    Resolution:

    If GIMP 3.x is required as the machine-wide installation, use the following approach

     

    1. Upgrade the existing machine-wide GIMP 2.10.x installation to GIMP 3.x using the organization's standard software deployment method.
    2. Do not rely on the GIMP 3+ (User) Software Updater entry to perform the machine-wide GIMP 2.x to 3.x major-version upgrade.
    3. After the machine-wide installation has been standardized to version 3.x, remove/uninstall the unnecessary per-user GIMP 3 installations to avoid duplicate installations and confusing Software Updater results.

    Note also, Software Updater by design does not perform major versions upgraded, but these have to be performed using the organization's standard software deployment method.

  • How to reset two factor authentication (2FA) for a WithSecure Business Account (Elements, Partner Portal, eService Portal) user account

    Read more
    Issue:

    How to reset two factor authentication (2FA) for a WithSecure Business Account (Elements, Partner Portal, eService Portal) user account. 

    Example scenarios:

    • User has a new mobile device and wants to move or transfer the authenticator to the new device 
    • Device that had the multi factor authentication (MFA) application broke or has been lost 
    Resolution:

    If you still have access to the old authenticator device, you can move the authenticator to a new device by logging in with the existing authenticator to the Elements portal, where you can remove the old authenticator and add a new one: 

    1. Log in to the Elements portal: https://elements.withsecure.com
    2. Click on the user icon in the top-right corner 
    3. Go to My settings 
    4. Click on the Change button on the right side of the Multi-factor Authentication enabled text
    5. Log in with your existing authenticator codes
    6. Click on the Remove button on the right side of the Google authenticator or similar text
    7. Confirm the removal by authenticating again with your username, password and authenticator code

    Once the existing authenticator has been removed, simply click on the add button to add your new authenticator.

    Note: Partner Portal and eService Portal users can also log in to the Elements portal and change the MFA settings.

    If you do not have access to the old device, to reset the MFA, ask another administrator to delete your user account and then they can create a new administrator account for you. When the account is re-created, you will get a new Welcome email that includes a temporary password which you can use to log in to the account and then set up a new password and configure MFA. If you do not have another administrator on the company account and you have a Partner Managed subscription, you should contact your partner and they can delete the user account. 

    NOTE: If you are a WithSecure partner user with access rights to the Partner Portal, your account cannot be fully deleted through the Elements portal. You need to ask a partner colleague to create a support case through the Partner Portal to have the user account deleted. The same applies for eService portal users, contact your WithSecure partner so that they can open a support case through the Partner Portal to have your user account deleted. 

    To delete the user account, another administrator can follow these steps:

    1. Log in to the Elements Security Center
    2. Navigate to Management > Organization Settings > Security Administrators
    3. Click on the user you want to delete
    4. Click Delete 
    5. Confirm the deletion 
  • Elements subscription key is showing incorrect expiry date in the Elements Security Center portal

    Read more
    Issue:

    Incorrect expiry date is shown for an Elements subscription on the Elements Security Center portal's Management > Subscriptions page.

    Applicable products:

    • Elements Endpoint Protection (Elements EPP for Computers and Servers)
    • Elements Endpoint Detection and Response (EDR)
    • Elements Collaboration Protection
    • Elements Exposure Management
    • Elements Identity Security for Entra ID
    • Elements Mobile Protection (Elements EPP for Mobiles) 

     

    Resolution:

    If an Elements subscription's expiration date doesn't match the date shown in the license certificate and is therefore wrong, if you are an end-customer, you need to contact your WithSecure reseller partner.

    If you are a WithSecure partner, you need to open a support case to the WithSecure Order Services team through the Partner Portal:

    1. Log in to the Partner Portal
    2. Navigate to Support > Contact Support
    3. Click Create Case 
    4. Select as Case Type: Order And Invoice Assistance 
    5. Enter rest of the information
    6. Click Next 

     

Identity Security

  • Error "Cannot validate argument on parameter" when updating Azure Entra ID Identity script

    Read more
    Issue:

    Error when updating Azure Entra ID Identity script;

    "ERROR during Azure deployment: Cannot validate argument on parameter 'Tenant'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
    Collecting information on failed deployments..."

    Resolution:

    Do make sure that any older or previous script is removed before running a newer script.

     

    1. Go to Azure and open the Cloud Shell
    2. Cleanup the old script files from their Azure shell using rm -r withsecure
    3. Upload the new script to the shell and unzip it
    4. Change directory to the withsecure folder using cd withsecure
    5. execute the update command: ./deploy.ps1 -update $true

Exposure Management

View all
  • How to exclude subdomain from being scanned by Elements Exposure Management Web Scan?

    Read more
    Issue:

    How to exclude subdomain from being scanned by Elements Exposure Management Web Scan? We want to block the scan for accessing specific sub-domain URL. 

    Resolution:

    If you want to exclude or block the Elements Exposure Management Web Scan from accessing a subdomain, you can enter the subdomain that you want to exclude or block in the Scan access rules section in your Web Scan Template.

    The Scan access rules can be used to control which part of the application the scanner is allowed or not allowed to access. Rules can be specified as an URL, regular expression or external regular expression. Access to domains different than a target domain is blocked by default. You can allow access to URL in different domain by specifying allow access URL rule or external regular expression rule. External regular expression rules are interpreted in the context of the URL specified in the rule. Regular expression rules work only in relation to target domain.

    Steps to add a scan access rule in the Web Scan template:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Scan templates page
    3. Go to the Network scan templates tab
    4. Click Add web scan template or modify existing template
    5. In the Scan settings step, scroll down to the Scan access rules section
    6. Select Block from the drop-down menu and enter one of the following:
      1. Url
      2. Regular Expression
      3. External Regular Expression
    7. Click Finish
  • Elements Exposure Management Network scan stuck at "Running" status for more than 24 hours

    Read more
    Issue:

    Elements Exposure Management Network scan (system scan) stuck at "Running" status for more than 24 hours

    Resolution:

    If you are using you own internal Elements Exposure Management Scan node and scans are stuck in "running" status for a very long time, we recommend to make sure that the scan node has enough processor (CPU) performance, memory (RAM) and disk space available. 

     

    Scanning multiple scan targets at a time is a very resource heavy task, so if scans take a long time, we recommend to check that the server is up to the task. 

     

    You can from the scan group settings adjust how many scan targets are scanned simultaneously. This can improve scan performance in cases where system resources are at their limit on a scan node server:

    1. Log in to the Elements Security Center portal 
    2. Navigate to the Security configurations > Scans > Network scans page
    3. Click on the three dots for a scan group and click Edit scan group
    4. In the Group details section, modify the Max system scans value to a smaller amount.

     

    To check if the issue is caused by a lack of resources, you can start a network scan for one scan target. If the network scan goes through faster on one scan target, then the issue is with the scan nodes resources. 

  • How to collect Discovery scan or Network scan logs for Elements Exposure Management?

    Read more
    Issue:

    How to collect Discovery scan or Network scan logs for Elements Exposure Management from the Elements Security Center portal? We want to investigate why a scan has failed.

    Resolution:

    To collect and download Elements Exposure Management Discovery scan logs from the Elements Security Center portal:

    1. Log in to the Elements Security Center portal 
    2. Navigate to the Security configurations > Scans page
    3. Go to the Discovery scans page
    4. Click on the three dots on the right side of a discovery scan and click View scan logs 
    5. Click Download from the bottom of the Discovery scan log window 

    To collect and download Elements Exposure Management Network scan (System scan) logs from the Elements Security Center portal:

    1. Log in to the Elements Security Center portal 
    2. Navigate to the Security configurations > Scans page
    3. Go to the Network scans tab
    4. Expand a scan group to view all the scan targets
    5. Click on the three dots on the right side of a scan target and select View scan logs 
    6. Click Download from the bottom of the Network scan log window

    Note: Network scan logs are downloaded one scan target at a time. 

  • When requesting a scan node license in Elements Exposure Management Portal, the error "No scan node licenses available. All licenses are currently in use" is displayed.

    Read more
    Issue:

    When requesting for a new scan node license in WithSecure Elements Exposure Management portal, user is getting error:

    • "No scan node licenses available. All licenses are currently in use"
    • "Number of allowed scan node licenses has been reached".

    How to delete / release the Elements Exposure scan node license? 

    Resolution:

    By default, customers can download five (5) Elements Exposure Management scan node license files (trial customers can download 1). When a scan node license file download takes place, the counter is decreased by one. However, unregistering a scan node in the Elements Exposure Management portal's Security configurations > Scans > Scan nodes page will not release the license. It is meant that if you want to move a scan node to a new server, you should use the old .fsrl license file on the new server. Do note that the same license file is not allowed to be in use on two scan node servers at a time.

    If you have misplaced (lost) a previously downloaded scan node license file and you would like to release the license to be used again, it needs to be released by WithSecure support.

  • Configuring different scan schedule at scan target level instead of scan group in Elements Exposure Management

    Read more
    Issue:

    If I have an Elements Exposure Management network scan group with a scan schedule configured. Can we use different scan schedule for specific scan targets within the scan group? 

    Resolution:

    To configure different scan schedule at the scan target level instead of scan group:

    1. Log in to the Elements Security Center portal
    2. Navigate to the Security configurations > Scans page
    3. Open the Network scans tab,
    4. Expand a scan group.
    5. Locate the scan target, click the three dots on the right side of the scan target
    6. Select Edit scan settings
    7. Click Next until the Other settings page
    8. Eble Schedule for the scan target
    9. Configure the new schedule or use the pre-configured system scan template
    10. Click Finish to save.

    Note: We cannot skip the scheduling, but you may turn off the Run indefinitely option and set the Number of times to scan to 1.

Common Topics

View all
  • Where can I find the list of supported products for WithSecure Software Updater?

    Read more
    Issue:

    How to check for which software WithSecure Software Updater offers patches? Is there a list of supported vendors for WithSecure Softeware Updater? 

     

     

    Resolution:

    You can find the list of supported products for which WithSecure Software Updater feature offers patches by clicking here: Vendors included in WithSecure Software Updater - WithSecure™

  • How to troubleshoot Security Cloud?

    Read more
    Issue:

    How to troubleshoot Security Cloud connectivity issues. 

    This article applies to the following products:

    • Elements EPP for Computers
    • Elements EPP for Servers 
    • Business Suite Client Security 
    • Business Suite Server Security
    Resolution:
    What is Security Cloud?
    When Security Cloud is enabled on WithSecure endpoint products, it connects to WithSecure Backend to check reputation and other objects. WithSecure endpoint products have database updates which can detect the malware without connection to cloud, but, to check the reputation we need cloud connection. There is the local cache, but it comes first from the cloud, where the whitelisting of false positives is done.
      Disabling Security Cloud is not recommended as there are many features that are dependent from Security Cloud, like:
      • DeepGuard with cloud connection:
      Unsigned processes reported as trusted by ORSP will be excluded from deep monitoring by DeepGuard
      • DeepGuard with no cloud connection:
       Big performance loses in operations of 3rd party applications
       Unsigned files will not be excluded
      • Application control with cloud connection:
      Rules depending on prevalence rating and reputation will be working fine
      • Application control with no cloud connection:
      Unsigned files reported as trusted by ORSP will be excluded from scanning by local engines
      Rules depending on prevalence and reputation will not work
      Feature is partially not operational 
      • File scanning with cloud connection:
      Unsigned files reported as trusted by ORSP will be excluded from scanning by local engine
      • File scanning with no cloud connection:
      Unsigned files will not be excluded
      Some performance loses on file access
      • Browsing protection with cloud connection:
      Works without restrictions
      • Browsing protection with cloud connection:
      Will not work at all as features fully depend on Security Cloud
      Feature is partially not operational 
      • Web Traffic Scanning with cloud connection:
      For URLs reported as trusted and prevalent by ORSP content returned by the server will be scanning
      • Web Traffic Scanning with no cloud connection:
      WTS will scan all responses of all URLs intercepted causing big performance issues
      Big performance issues on web browsing
      How does WithSecure Security cloud work?
      The Security Cloud collects information about unknown applications and websites, malicious applications and malicious activities that exploit the information of users of websites. When you subscribe to Security Cloud, we collect important information so that we can provide you with the security services you subscribe to and enhance the security of our other services. For this reason, and for the operation of our services, we need to collect security information about unknown files, suspicious device activity or visited URLs.

      Security Cloud does not monitor your Internet usage and does not collect information about websites that have already been analyzed or about unsafe applications installed on your computer.

      How do I troubleshoot connectivity issues related to Security cloud?
      When you enable Security Cloud, you also need to whitelist the following domains on your Firewall, as the endpoints need to communicate to Security Cloud.

      • *.f-secure.com
      • *.fsapi.com
      Note: The domains mentioned above needs to be whitelisted to your firewall or proxy. In case your have enabled some proxy in your environment, the client reads it via discovery service and tries to connect to *.fsapi.com through it. 

      Client writes that information in registry: 

      [HKEY_LOCAL_MACHINE\SOFTWARE\F-Secure\Ultralight\Settings\proxy] 
      "value"=(REG_SZ):http://proxy.example.intern:3128
      "access"=(REG_DWORD):1

       

      Example when network queries fail to connect to F-Secure back-end, from fsscorplug.log you will see how the client tries to connect to one of our backend servers and fails:

      2021-11-12 17:40:30.152 [15c0.1d1c] .W: CurlQuery::completeWithStatus: failure on handle 0000023C45E27C50 5 Could not resolve proxy: proxy.example.intern
      2021-11-12 17:40:30.152 [15c0.1d1c] .W: fs::xrssdk::HTTPQueryTask::update_http_stats: http error 111 (5) for http task 0000023C45E9AC20, time 4 ms
      2021-11-12 17:40:30.152 [15c0.1d1c] .W: ipc_impl::on_async_complete_ex: winrpc call completed err 111
      2021-11-12 17:40:31.751 [15c0.1d1c]  I: fs::xrssdk::DoormanCache::update: doorman cooldown is off, ttl: 15, fserr: 0
      2021-11-12 17:43:02.424 [15c0.1d1c] .W: CurlQuery::completeWithStatus: failure on handle 0000023C468C1D90 28 Operation timed out after 1006 milliseconds with 0 bytes received
      2021-11-12 17:43:02.424 [15c0.1d1c] .W: fs::xrssdk::HTTPQueryTask::update_http_stats: http error 201 (28) for http task 0000023C45E76790, time 1006 ms
      2021-11-12 17:43:02.424 [15c0.1d1c] .W: ipc_impl::on_async_complete_ex: winrpc call completed err 201
      2021-11-12 17:48:02.964 [15c0.1fe8]  I: ipc_impl::stopRpcServer: MSRPC Server stopped

      The log can contain fserr 101 or 218 which are actual network failures. 

      The log shows some results from cache, as the queries are stored for 2 hours in cache, meaning if you just allowed our domains in firewall, client will still use cache queries for another 2 hours. Cache cleanup is for faster results to test the connectivity. you can clean the cache directly from client as follows:

      1. Open a Command prompt with administrator priviledges
      2. Stop the network hoster: net stop fsulnethoster
      3. Remove all files from "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\F-Secure\fsscor"
      4. Start network hoster: net start "fsulnethoster
      If you have allowed *.f-secure.com and *.fsapi.com in your firewall, you can test the connection in two ways:
      • Opening the URLs on Browser and they should respond with ok
      https://baseguard.doorman.fsapi.com/doorman/v1/healthcheck
      https://doorman.sc.fsapi.com/doorman/v1/healthcheck
      https://a.karma.sc2.fsapi.com/healthcheck
      • Use WithSecure Connectivity Tool, which is available in the installation folders of Elements Endpoint Protection (EPP for Computers and EPP for Servers), Business Client Security and Business Suite Server Security. With the tool you can view the list of addresses the product connects to and check the connectivity towards them.

      Note: For Client Security the tool is available in 15.20 and later versions, and for Server Security 15.10 and later. 

      The tool is located in the following folder:

      • Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\wsconnectionchecker.exe
      • Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\wsconnectionchecker.exe
      • Elements EPP for Computers and EPP for Servers: C:\Program Files (x86)\F-Secure\PSB\ui\wsconnectionchecker.exe

       For older Client Security and Server Security releases, you can download the tool from here: https://download.sp.f-secure.com/connectivitytool/ConnectionChecker.exe

      What logs do should be checked in case of such behaviour?

      fsscorplug.log
      .W: fs::rs::WinSocket::Impl::waitForConnection: Wait failed: 258
      .W: fs::rs::WinSocket::Impl::connect: Conection timeout: doorman.sc.fsapi.com

      CcfPluginState.log
      .W: Filter2::ContentFilter2State::ReplyDriverMessage: Failed to reply message 2222

      orspplug.log
      .W: fs::rs::WinSocket::Impl::waitForConnection: Wait failed: 258
      .W: fs::rs::WinSocket::Impl::connect: Conection timeout: doorman.sc.fsapi.com

      DeepGuard.log
      .W: SecurityCloud::Query: ORSP failed for 0dac68816ae7c09efc24d11c27c3274dfd147dee (0, 0)
      .W: SecurityCloud::Query: Too many successive ORSP failures. Further failure logs will be suppressed
      .W: SecurityCloud::Query: ORSP query took 3016ms

      transportAgent.log (Email and Server Security only)
      .W: FSecure.Ess.Fsscore.Client: FSSCORE query for URL('http://schemas.microsoft.com/office/2004/12/xxxx') Failed, error=Timeout 
      .W: FSecure.AntiVirus.Exchange.Transport.FSMessageScanner: Can't get a response from FSSCORE. The following URLs will not be scanned 

    • High CPU usage and latency opening Excel files when DeepGuard is running

      Read more
      Issue:

      High CPU usage and latency opening Excel files when DeepGuard is enabled on a Windows computer.  Application is slow to start.

      Resolution:

      If opening Excel files is slow and / or CPU usage is high, we recommend to check the following for Elements Endpoint Protection and Business Suite (Client Security and Server Security) devices.

       

      For Elements Endpoint Protection (Elements Agent) devices:

      • Run the wsconnectionchecker.exe to make sure the connectivity to the WithSecure backend services and Security Cloud is OK: C:\Program Files (x86)\F-Secure\PSB\ui\wsconnectionchecker.exe
      • Make sure that Security Cloud is enabled. From the Elements profile, go to the Real-time scanning settings page and verify that Upload suspicious samples to WithSecure Security Cloud is in use. 
      • Make sure that the Application Control Global rule is not set to Allow and monitor all applications.
      • Make sure that you have not created Application Control rules which have only SHA1 or SHA256 hash as a condition. Hash conditions must always be paired with another condition, so that the hash value doesn't need to be calculated each time an application is started.  

      For Business Suite Client Security and Server Security devices: 

      • Run the Connectivity tool to make sure that the device has access to the Security Cloud:
        • Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\fsconnectionchecker.exe
        • Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\fsconnectionchecker.exe
      • Check that Security Cloud is enabled in the policy. This can be checked from Policy Manager Console's Settings > Windows > Real-time scanning settings page
      • Make sure that the Application Control Default rule applied to untrusted applications is not set as Report. 

    Business Suite

    View all
    • Client Security or Server Security fails do download update from Policy Manager, AUA.log shows "try later" error

      Read more
      Issue:

      Client Security or Server Security are unable to download malware definition database and engine updates from the Policy Manager Server or Proxy due to the update check ending with "try later" result:

      I: Connecting to <Policy Manager Server or Policy Manager Proxy Server address>/guts2
      I: Update check completed with 'try later' result

      Resolution:

      This could happen in case the Policy Manager Server/Policy Manager Proxy Server is attempting to download the updates (but unable to reach the web update server), and respond with "try later".

      You need to ensure that the Policy Manager Server/Policy Manager Proxy Server is able to reach the web update server. Do allow the connectivity to *.withsecure.com and *.fsapi.com in the Policy Manager Server's HTTP proxy or firewall.

      We recommend to run the WithSecure Connection Checker tool to make sure your servers and hosts are allowed to connect to all the necessary addresses: https://download.withsecure.com/connectivitytool/ConnectionChecker.exe

      If you Policy Manager Server requires HTTP proxy to reach the WithSecure GUTS2 update server, you need to define the proxy server address in the fspms.proxy.config file. 

      Windows: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\ fspms.proxy.config

      Linux: /var/opt/f-secure/fspms/data/fspms.proxy.config

      If issue remain, try to manually delete old updates from the Policy Manager Server's GUTS2 updates folder: 

      Here are the steps how to manually reset on a Windows Server the Policy Manager Server's updates GUTS2 folder:

      1. Stop the Policy Manager Server service by using Command Prompt
        1. net stop wspms
      2. Delete the contents of the following folder: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\guts2\updates
      3. Start the Policy Manager Server service: 
        1. net start wspms

      On Linux Servers, delete contents of  /var/opt/f-secure/fspms/data/ and restart the server.

      If you are still experiencing update download or installation issues on your Client Security or Server Security clients, you can run the FSAUA-Reset.exe tool on the clients: Support tools - WithSecure™ 

      It resets the WithSecure Automatic Update Agent (AUA) agent on the clients and forces them to re-download the updates. 

    • The Policy Manager "Denied website blocked" alert doesn't include the website URL address

      Read more
      Issue:

      There are "Denied website blocked" alerts in the Policy Manager Console's Alerts tab that don't include the website URL address. Why are the website URL addresses not shown in the alerts sent from the Client Security and Server Security devices?

      Resolution:

      The website URL address will not be shown by default if the address has been added by the administrator to the Web Content Control > Disallowed sites list.  

      • Settings >Windows > Web Content Control > Disallowed sites

      This is due to user privacy reasons.

      If you want to include the URL addresses in alerts that are not about harmful or malicious websites being blocked, you can enable the Include the blocked URLs in all alerts setting. This setting will change the behavior so that the URLs addresses are included when:

      • Website URL address has been added to the Disallowed sites list by the administrator
      • When Connection Control blocks a website during an active banking session
      • When a website belonging to a disallowed Web Content Control category is blocked

      Steps to enable the Include the blocked URLs in all alerts setting:

      1. Log in to the Policy Manager Console
      2. Select a host or policy domain from the domain tree
      3. Go to the Settings tab
      4. Navigate to the Windows > Browsing Protection settings page
      5. In the General section, enable the Include the blocked URLs in all alerts setting
      6. Distribute the policy (Ctrl + D)
    • Getting 'License already expired' error when installing Linux Security 64

      Read more
      Issue:

      We are getting the "license already expired" error message during the Linux Security 64 installation on a client machine. 

      Resolution:

      If your Business Suite license is valid and you are able to log in to the Policy Manager Console, but you still get the "License already expired" error when installing Linux Security 64 on a Linux device, then the most likely reason is that you are using an old installation package for Linux Security 64.

      We recommend you to:

      1. Remove the previously imported Linux Security 64 .jar installation package from the Policy Manager Console
      2. Download the latest Linux Security 64 .Jar installation package from our downloads page and import it to the Policy Manager Console: Linux Security - WithSecure™ 
      3. Export a new installer and run in on the Linux device

      Note: Before running the installer, make sure that there are no files left of the previous failed installation: Uninstalling the product | Linux Security 64 | Latest | WithSecure User Guides 

      If you are installing Linux Security 64 as a stand-alone installation in an isolated or offline environment without Policy Manager managed mode, there is also a need to use a new content package (withsecure-updates.zip) to update the definitions: Creating the content package for isolated environments | Linux Security 64 | Latest | WithSecure User Guides 

    WithSecure Cloud Protection for Salesforce

    View all
    • How to upgrade Cloud Protection for Salesforce and is there a rollback option ?

      Read more
      Issue:

      How to upgrade Cloud Protection for Salesforce? Is there any roll-back option available after upgrade to latest version so that incase if there is any issue with the new version then we can rollback to old version.

      Resolution:

      The latest version of the Cloud Protection for Salesforce solution is always available in Salesforce AppExchange. Upgrading preserves all existing settings and analytics data.

      WithSecure Cloud Protection is listed on Salesforce AppExchange here: https://appexchange.salesforce.com/listingDetail?listingId=a0N3A00000EFntJUAT.

      1. Log in to Salesforce with your System Administrator account.
      2. Go to the Salesforce AppExchange marketplace, find the WithSecure Cloud Protection application, and click "Get It Now" to start installation.
      3. Depending on whether you are installing the application to your production Salesforce org or Sandbox, choose Install in production or Install in Sandbox and agree to the terms and conditions.

      More details can be found here:

      Upgrading the application | Cloud Protection for Salesforce | Latest | WithSecure User Guides

      We suggest to try things out first on the Sandbox, then Production environment.

      We would prefer to fix any issues with the new version, rather than use the old one. Technically, it is possible to uninstall the new version and install the previous one, but that should be considered as the last resort.

    • How to download the latest version of WithSecure Cloud Protection for Salesforce?

      Read more
      Issue:

      How to download the latest version of WithSecure Cloud Protection for Salesforce?
       

      Resolution:

      The latest version of WithSecure Cloud Protection for Salesforce version can be downloaded from our product Downloads page.

    • How to increase the Scan Quota Increase in the Cloud Protection for Salesforce when getting Error monthly scan usage quota limits exceeded ?

      Read more
      Issue:

      How to increase the Scan Quota in Cloud Protection for Salesforce when getting error: "monthly scan usage quota limits exceeded" ?

      1. What’s the impact on the service when we hit the monthly scan quota limit?
      2. What are the options available to optimize the scan quota usage?
      Resolution:

      You are getting that email alert because they have reached the total monthly scan quota in your purchased license. 

      If you want it to be increased, then you have to contact your sales representative or WithSecure sales contact (account owner) to purchase more licenses.

      You may consider to optimize the scan quota usage as below:

      1. Currently there is no hard limits in Cloud Protection for Salesforce, so everything will still work after the total monthly scan quota limit has been reached. Having said that, there is still a need for you to consider on purchasing license to increase the monthly scan quota.
      2. In order to optimize the scan quota usage, you could consider to limit the scanned file extension, exclude certain file extensions and set how long you will trust the cache data. Apart from that, you could also consider to limit the licensed users and locations for the objects to be scanned (for example, selected objects only).

    Other WithSecure Products

    View all

    Business Suite

    • Client Security or Server Security fails do download update from Policy Manager, AUA.log shows "try later" error

      Read more
      Issue:

      Client Security or Server Security are unable to download malware definition database and engine updates from the Policy Manager Server or Proxy due to the update check ending with "try later" result:

      I: Connecting to <Policy Manager Server or Policy Manager Proxy Server address>/guts2
      I: Update check completed with 'try later' result

      Resolution:

      This could happen in case the Policy Manager Server/Policy Manager Proxy Server is attempting to download the updates (but unable to reach the web update server), and respond with "try later".

      You need to ensure that the Policy Manager Server/Policy Manager Proxy Server is able to reach the web update server. Do allow the connectivity to *.withsecure.com and *.fsapi.com in the Policy Manager Server's HTTP proxy or firewall.

      We recommend to run the WithSecure Connection Checker tool to make sure your servers and hosts are allowed to connect to all the necessary addresses: https://download.withsecure.com/connectivitytool/ConnectionChecker.exe

      If you Policy Manager Server requires HTTP proxy to reach the WithSecure GUTS2 update server, you need to define the proxy server address in the fspms.proxy.config file. 

      Windows: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\ fspms.proxy.config

      Linux: /var/opt/f-secure/fspms/data/fspms.proxy.config

      If issue remain, try to manually delete old updates from the Policy Manager Server's GUTS2 updates folder: 

      Here are the steps how to manually reset on a Windows Server the Policy Manager Server's updates GUTS2 folder:

      1. Stop the Policy Manager Server service by using Command Prompt
        1. net stop wspms
      2. Delete the contents of the following folder: C:\ProgramData\WithSecure\NS\Policy Manager\Policy Manager Server\data\guts2\updates
      3. Start the Policy Manager Server service: 
        1. net start wspms

      On Linux Servers, delete contents of  /var/opt/f-secure/fspms/data/ and restart the server.

      If you are still experiencing update download or installation issues on your Client Security or Server Security clients, you can run the FSAUA-Reset.exe tool on the clients: Support tools - WithSecure™ 

      It resets the WithSecure Automatic Update Agent (AUA) agent on the clients and forces them to re-download the updates.