100% CPU. - WDAEMON High Usage | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. 100% CPU. - WDAEMON High Usage

100% CPU. - WDAEMON High Usage

  • R

    Hello,

    I have recently observed high CPU usage by wdaemon process.

    The server, which is dedicated to mdaemon, has 16 cores operating at 3Ghz.

    I am currently using the latest release, version 23.5.2, and have not encountered this issue with any previous releases.

    Thank you in advance

    Attachments:

    wdaemon-100.png
    0 likes
  • H

    Hi,

    I have the same problem, and I think I found the cause.

    The latest version of Outlook ( Version 2401 Build 17231.20194 ) has a broken Activesync, which prevents it from syncing properly.
    There will be many more connections from these clients than before.
    See the size of AirSync*.log, these grow much more.

    Blocking UA *16.0.17231.20036* i MDaemon ActiveSync removed the load...

    I think the clients need to roll back to version 16.0.17126.20132, according to the link below.

    "C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17126.20132

    See for example https://help.zoho.com/portal/en/community/topic/outlook-eas-broken-with-version-2401

    0 likes
  • T

    @Reuben As @Håkan mentioned, if there are Outlook (for Windows desktop) clients running the latest update, version 2401 released February 1, 2024, there is a known issue causing problems with Outlook ActiveSync profiles.  This will likely cause higher than normal CPU usage on the server and increased AirSync log file sizes. The Outlook clients may not have any new data after February 1 and/or may see mailboxes re-sync or attempt to re-sync and hang.

    Microsoft has acknowledged the issue and is investigating. 

    https://support.microsoft.com/en-us/office/outlook-desktop-exchange-activesync-connections-stopped-working-in-version-2401-da2dc0dd-297e-48ba-b6d9-ab18f5d522fc

    I was able to reproduce the issue and follow the steps @Håkan has mentioned above to downgrade my Outlook client to version 2312 and the issue disappeared. 

    I would also recommend selecting File > Office Account > Update Options and choose the option to disable updates to prevent Outlook from upgrading back to 2401. 

    0 likes
  • T

    @Håkan Hi

    How do you block in Mdaemon a specific Outlook version? And I guess if you do that the clients could not connect to Mdaemon to check the mailbox, right?

    0 likes
  • T

    @Tasagore 

    Open MDaemon and select Setup > ActiveSync, select the Security tab.  Here you can block device-type or user agents from connecting to MDaemon's ActiveSync service.  Unfortunately, there is not an option to block a specific version. 

    https://help.mdaemon.com/mdaemon/en/activesync--security.html

    Another option to block a user's client is in the ActiveSync > Clients menu in the Account Editor for the user.  Right click on the client you'd like to block and select 'Block this client.' 

    https://help.mdaemon.com/mdaemon/en/ae_activesync_clients.html

    The specific client ID will now appear on Block list in the Setup > ActiveSync > Security menu.  

    The blocked the client will get an error when attempting to connect to MDaemon and an entry will be logged in the AirSync-YYYY-MM-DD.log file showing the attempted connection and MDaemon responding with 403/Forbidden.

    0 likes
Please login to reply this topic!