Share via

Problem with FMS service in Exchange 2019

Aleksandr Aleksandr 20 Reputation points
2026-03-03T11:53:48.55+00:00

Hi everyone!

There is a problem with the Microsoft Filtering Management Service, which is responsible for managing filters in Exchange.

At some point, the service stopped working, that is, if you look at the logs, the following events are observed:

The FIP-FS Scan Process failed initialization. Error: 0x80010105. Error Details: The server threw an exception.

Faulting application name: scanningprocess.exe, version: 15.2.1748.38, time stamp: 0x68c2bb95

Faulting module name: scanningprocess.exe, version: 15.2.1748.38, time stamp: 0x68c2bb95

Exception code: 0xc0000005

Fault offset: 0x000000000005c72d

Faulting process id: 0x2408

Faulting application start time: 0x01dcab02fb54e95c

Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\scanningprocess.exe

Faulting module path: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\scanningprocess.exe

Report Id: piiremoved

Faulting package full name:

Faulting package-relative application ID:

This error occurs on Exchange servers that do not have mailbox databases and cannot have message queuing issues.
--------------------------------------

I have come all the way that is indicated in this article:

https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-exchange-on-premises-transport-queues/ba-p/3049447

I also tried to solve the problem with this appeal:

https://learn.microsoft.com/en-us/answers/questions/302892/the-fip-fs-scan-process-failed-initialization-erro?page=5#answers

Neither way helped me.

The FMS service itself starts, but literally after a couple of minutes it stops and I see the errors indicated above in the logs.

Also, certain CUs or regular Windows updates were not installed.

Hope for your support to find a solution.

Thank you!

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments
Answer accepted by question author
  1. Q&A Assist
    2026-03-03T11:54:03.4333333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The symptoms indicate a failure in the FIP-FS scanning engine (scanningprocess.exe) used by the Microsoft Filtering Management Service (FMS). A common root cause for FIP-FS scan failures and related crashes is missing or corrupted engine files under the FIP-FS engines directory.

    On Exchange servers, when the FIP-FS engine cannot initialize correctly, it can generate FIP-FS errors and may cause messages to be placed in the Poison queue or cause FMS-related failures. The documented cause is missing required files in the FIP-FS engines folder:

    <Exchange_Installation_Path>FIP-FS\Data\Engines\amd64

    To remediate this class of FIP-FS engine problems, use the supported file-restore method:

    1. On an unaffected Exchange 2019 server (same CU level), go to: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data\Engines\amd64
    2. Copy all files from that folder.
    3. On the affected Exchange 2019 server, stop the Microsoft Filtering Management Service (FMS) and any dependent services.
    4. On the affected server, navigate to the same path: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data\Engines\amd64
    5. Replace the contents of this folder with the files copied from the healthy server (overwrite existing files).
    6. Start the Microsoft Filtering Management Service again and monitor the Application and System event logs for new FIP-FS or scanningprocess.exe errors.

    If there is no other healthy Exchange server at the same build level from which to copy the FIP-FS engine files, the supported path is to open a case with Microsoft Support to obtain the correct engine files for the installed CU.

    If, after restoring the engine files, FMS still crashes, collect the latest FIP-FS and Application log entries and a crash dump of scanningprocess.exe, then escalate to Microsoft Support for deeper analysis, as the next steps are not covered in the provided documentation.

    References:

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Aleksandr Aleksandr 20 Reputation points
    2026-03-03T12:19:39.5133333+00:00

    I have tried use files from folder: C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data\Engines\amd64

    from a healthy server, however this did not help.

    I also tried to delete content in the C :\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data\Engines\amd64 folder, but I am hindered by the scanningprocess.exe processes, which I cannot close even if the Exchange server is put in maintenance mode and all the necessary services are stopped.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.