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

Andrey 181

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

Mark Stott 21 Reputation points

2022-01-01T07:48:01.883+00:00

Exactly the same issue here. Got called out at 7AM to issues with email delivery. I'm logging with Microsoft support.
Rob Wnuk 1 Reputation point

2022-01-01T11:22:52.54+00:00

Having the same issue!!!! Please keep this post updated! Thanks in advance!
Mike Fynboh 1 Reputation point

2022-01-01T12:16:27.583+00:00

Exchange 2019 as well.
Thanks for the heads up!
Markus Hnatek 6 Reputation points

2022-01-01T12:17:17.497+00:00

Can't convert "2201010001" to long looks like a version number including the date (20)22.01.01.0001 ... as max-long is 2147483647 it worked for (20)21.12.31.xxx but not for (20)22.01.01.0000
Fits the first Log entry today at 02:20 am :(

As mentioned Disable-AntimalwareScanning.ps1 helps
Brandon C 11 Reputation points

2022-01-01T12:29:21.423+00:00

I too am having the issue. Exchange 2016
Terence Swales 6 Reputation points

2022-01-01T12:31:29.223+00:00

same issue here. Disabling malware scanning works and queues have come down but they are not clearing completely with an average of 70 mails still stuck in the submission queue on each of the 3 servers for this client and experiencing mail delays because of this. Works fine at another client i must add.
Kozerski, Raffael 6 Reputation points

2022-01-01T13:46:32.657+00:00

queue suspend and resume will help here:

Get-Queue | Get-Message | Suspend-Message

Get-Queue | Get-Message | Resume-Message
Cam Matson 6 Reputation points

2022-01-01T15:41:06.347+00:00

We have had the same issue for the last 6 hours, had tried everything spoken about here but our mail Q's kept on building. It also turns out you need to check for any Transport rules that may check mails for Credit card numbers, attachments as they use the same engine, disable these and mail will work.
Кирилл Семенов 1 Reputation point

2022-01-02T02:02:23.213+00:00

Exchange 2019 CU11 as well.
Thanks for the heads up!
jhon heaps 1 Reputation point

2022-01-02T13:52:58.37+00:00

Yes, those bugs will never stop :)
Think to switch to Linux and say goodbay to these bugs and stop asking support from stupid guys.
For me, saying goodbye to Microsoft has never been easier, or so satisfying :)

Accepted answer

Corbett Enders 101 Reputation points

2022-01-02T01:01:09.413+00:00

Office Exchange Team blog post here: https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447
Please sign in to rate this answer.

2 people found this answer helpful.
Kozerski, Raffael 6 Reputation points

2022-01-02T09:01:26.6+00:00

yes, the "ResetScanEngineVersion.ps1" worked like a charme. After running and downloading the new Malware ScanEngine I enabled the Malware ScanEngine and everything works fine (Exchange 2016).
Thanks to all! Raffael

JV 6 Reputation points

2022-01-02T15:34:25.727+00:00

Did you have to put in maintenance mode? I think it just restarts the transport and then the Filtering management service?

Kozerski, Raffael 6 Reputation points

2022-01-02T15:59:07.003+00:00

No maintenance mode (only single mailbox server); the script stops and starts FMS and Transport Services.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

10 additional answers

MPB Support 1 Reputation point

2022-01-02T04:29:14.993+00:00

Setting malware bypass worked for me. Thanks
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Denis GILLET 1 Reputation point

2022-01-02T15:12:14.527+00:00

By the way, no problem on Edge servers even with malware scanning enabled.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

10 additional answers

Your answer