Microsoft Exchange FIP-FS Scan Engine failed to load after update 01/01/2022 0x80004005 Can't convert to long

Andrey 181 Reputation points
2022-01-01T07:15:19.513+00:00

Greetings and Happy New Year!

Tpday 01/01/200 faced this issue after auto update the FIP-FS (filtering management service) on our on-premium server MS Exenge 2016 21 KU with the latest security updates (KB5007409).

The FIP-FS "Microsoft" Scan Engine failed to load. PID: ХХХХХ, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long. (2201010002, 2201010003 etc)

Since the service is interconnected with the transport service, mail stops coming in and out, respectively.

And yes, as a workaround, disabling Disable-AntimalwareScanning.ps1 helps

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,483 questions
{count} votes

Accepted answer
  1. Corbett Enders 101 Reputation points
    2022-01-02T01:01:09.413+00:00
    2 people found this answer helpful.

10 additional answers

Sort by: Most helpful
  1. Maroiane Ghédira 31 Reputation points
    2022-01-01T15:11:46.783+00:00

    Hello,
    As a workaround you can just bypass malware filtering on all servers with a transport service restart afterwards (solution tested and validate)
    --> Set-MalwareFilteringServer -Identity <SERVER NAME> -BypassFiltering $true
    --> Restart-Service MSExchangeTransport

    3 people found this answer helpful.

  2. Brandon C 11 Reputation points
    2022-01-01T12:28:22.81+00:00

    I too am having the same issue. Exchange 2016.

    1 person found this answer helpful.

  3. Markus Hnatek 6 Reputation points
    2022-01-01T12:37:36.797+00:00

    Can't convert "2201010001" to ... long looks like a date + version number ... (20)22.01.01.0001 ... max-long is 2147483647 so it worked for (20)21.12.31.0000 but not for (20)22.01.01.0000. Fits the first log entries at 02:20 am today.

    Exchange 2019 latest CU ... Disable-AntimalwareScanning.ps1 ... queus are "empty" now

    1 person found this answer helpful.
    0 comments No comments

  4. Lawrence Patterson 6 Reputation points
    2022-01-01T14:24:10.987+00:00

    Hello, confirming that my Exchange 2016 CU22 is having a similar issue, started just after 8 PM EST, though my error is " The FIP-FS "Microsoft" Scan Engine failed to load. PID: 29572, Error Code: 0x80004005. Error Description: Can't convert "2201010002" to long. " which appears to be just slightly different from what I've seen.

    Also see https://borncity.com/win/2022/01/01/exchange-fip-fs-scan-engine-failed-to-load-cant-convert-2201010001-to-long-1-1-2022/ with a further confirmation.

    Can and will wait for a response from Microsoft, as we are in the middle of a downtime.

    1 person found this answer helpful.
    0 comments No comments