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

Mark Stott 21 Reputation points

2022-01-01T15:05:51.87+00:00

Update from Microsoft support - engineering team are aware of this issue and working on a fix at the moment.
Please sign in to rate this answer.

1 person found this answer helpful.
CirrusSR22Joe 1 Reputation point

2022-01-02T00:23:32.85+00:00

MarkStott, Any update from Microsoft?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Corbett Enders 101 Reputation points

2022-01-02T16:12:56.187+00:00

MS has released a fix. Go to the official post and read about it: https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-transport-queues/ba-p/3049447
Please sign in to rate this answer.

1 person found this answer helpful.
Chris Stephens 6 Reputation points

2022-01-03T15:14:13.29+00:00

Ok, worked after 2nd attempt

1st attempt took about 5mins!
2nd took 25mins longer downloadin!!

BUT, I don't have
Get-EngineUpdateInformation.ps1 in C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Get-EngineUpdateInformation

or Update-MalwareFilteringServer.ps1

I manually entered the previous command replacing the $true with false !
restarted the

Then restarted the Server for good measure!

where can I get the Get-EngineUpdateInformation.ps1 script?

Terence Swales 6 Reputation points

2022-01-03T15:18:19.597+00:00

just run this cmd "Add-PSSnapin Microsoft.Forefront.Filtering.Management.Powershell." to add the module in the exchange PS session then simply run the cmd Get-EngineUpdateInformation

JV 6 Reputation points

2022-01-03T15:18:36.033+00:00

Alternatvely, can verify by filtering Event Viewer with FIPFS. You should see something like this once you apply the official fix

EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1227.0
SignatureDateTime : 01/01/2022 03:29:06 AM -08:00
UpdateVersion : 2112330001
Sign in to comment

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

2022-01-01T15:47:51.64+00:00

this bypass worked for me! thanks so much. we were pulling our hair out trying to figure this out.

happy new year
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.
Samdi 46 Reputation points

2022-01-01T18:13:39.557+00:00

There are two methods to disable the malware scanning and fix the mail flow issues: See more: https://www.alitajran.com/exchange-mail-flow-breaks/
Please sign in to rate this answer.
Terence Swales 6 Reputation points

2022-01-01T18:35:43.763+00:00

nice one Samdi-4478
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