Exchange Scan Engine failed to load - Can't convert "2201010003" to long

Question

Exchange Scan Engine failed to load - Can't convert "2201010003" to long

Marco M 11

Hello,

we have this morning on multiple Exchange Servers (2013, 2016) error messages and no mails are routed:

Event ID: 5300 The FIP-FS "Microsoft" Scan Engine failed to load. PID: 51864, Error Code: 0x80004005. Error Description: Can't convert "2201010003" to long.

Event ID: 1106 The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unknown Error

For me it seems to have something to do with the new year date: 01.01.2022 -> converted 220101xxxxxx

This error occured on several Exchange Systems (Version 2013 and 2016) in diffrent networks and no mails are routed (interal and external).
The Servers have Exchange 2013 CCU19 Update or Exchange 2019 CCU10 Update and latest Windows Updates installed.

It all began tonight at about 2.00 in the morning CET.

Thanks in advance for any help

Best regards,

Marco

Brian Kirkley 11 Reputation points

2022-01-01T07:56:41.837+00:00

We had this same issue tonight, starting around 8pm Eastern.

This was the sequence that lead to Exchange not sending emails, until we disabled Anti-Malware on the transport service of every Exchange Server:

MS Filtering Engine Update process has successfully committed and handed off updates for Microsoft
Last Checked:2022-01-01T00:53:28Z
Last Updated:2022-01-01T00:53:38Z
Engine Version:1.1.18800.4
Signature Version:"1.355.1209.0"
Update Version:2201010001
Last Definition Update:‎2021‎-‎12‎-‎31T19:14:11.000Z
Update Path:http://amupdatedl.microsoft.com/server/amupdate

The scan process with PID: XXXXX was terminated. Reason: FailedEngineUpdate.

The FIP-FS "Microsoft" Scan Engine failed to load. PID: XXXXX, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long.

Once we disabled Anti-Malware, mail started flowing, and these errors all went away.

Tomorrow morning we will try re-enabling Anti-Malware and see if the error returns.
Mark Stott 21 Reputation points

2022-01-01T08:29:18.18+00:00

Exactly the same issue here. Got called out at 7AM to issues with email delivery. I've logged with Microsoft support & disabled Anti-Malware.
Marco M 11 Reputation points

2022-01-01T08:35:50.63+00:00

Thats what I did on all exchange systems - .\Disable-AntimalwareScanning.ps1 and restart Microsoft Exchange Transport.
After that all pending eMails were routed in the Mailboxes.

Thanks for your replys and happy new year.
Paul Lawrence 1 Reputation point

2022-01-01T09:24:30.86+00:00

Received the same error at around 3am GMT (United Kingdom). Fix was the same, disable anti malware policy.
asheroto 26 Reputation points

2022-01-01T10:18:41.29+00:00

Weird, same issue here, just started in the last day. No e-mails have been delivered since this error started.

Thanks for the path to disable antimalware scanning.
asheroto 26 Reputation points

2022-01-01T10:34:26.13+00:00

Looks like it's because they used a long variable type for the number which has a max integer value of 2,147,483,647, and the value in the error message 2201010003 ( 2,201,010,003 ) exceeds the max value.
asheroto 26 Reputation points

2022-01-01T10:36:13.39+00:00

With 32-bit... and Exchange is 32-bit... for now. :-)
Rizzo Andrea 1 Reputation point

2022-01-01T10:38:57.66+00:00

Hello, same issue mail flow freeze from 00:15 01.01 22
On all E2016 with last CU
Waiting on msexchange Team
WBR
Jay Drinkwater 1 Reputation point

2022-01-01T13:45:41.127+00:00

From https://learn.microsoft.com/en-us/cpp/cpp/integer-limits?view=msvc-170

LONG_MAX Maximum value for a variable of type long. 2147483647

Has the Y2K bug finally caught up with us?
pravin bedekar 6 Reputation points

2022-01-01T18:01:37.127+00:00

I also faced this issue and all mails are cleared after I disabled the Anti-Malware, but Mails are still getting delayed to end users, so kindly suggest
asheroto 26 Reputation points

2022-01-03T00:01:55.933+00:00

The fix has been released.
asheroto 26 Reputation points

2022-01-03T03:04:31.98+00:00

So I ran the PowerShell script, but still having issues! Same problem... What's weird is that event viewer does not report the error, but no e-mails will deliver. I restarted all services.

I then disabled anti-malware scanning again, restarted transport, and e-mails are flowing.

I also checked to ensure my engine date was as expected.... any ideas guys?

6 answers

Your answer

Brian Kirkley 11 Reputation points

2022-01-01T07:56:41.837+00:00

We had this same issue tonight, starting around 8pm Eastern.

This was the sequence that lead to Exchange not sending emails, until we disabled Anti-Malware on the transport service of every Exchange Server:

MS Filtering Engine Update process has successfully committed and handed off updates for Microsoft
Last Checked:2022-01-01T00:53:28Z
Last Updated:2022-01-01T00:53:38Z
Engine Version:1.1.18800.4
Signature Version:"1.355.1209.0"
Update Version:2201010001
Last Definition Update:‎2021‎-‎12‎-‎31T19:14:11.000Z
Update Path:http://amupdatedl.microsoft.com/server/amupdate

The scan process with PID: XXXXX was terminated. Reason: FailedEngineUpdate.

The FIP-FS "Microsoft" Scan Engine failed to load. PID: XXXXX, Error Code: 0x80004005. Error Description: Can't convert "2201010001" to long.

Once we disabled Anti-Malware, mail started flowing, and these errors all went away.

Tomorrow morning we will try re-enabling Anti-Malware and see if the error returns.
Mark Stott 21 Reputation points

2022-01-01T08:29:18.18+00:00

Exactly the same issue here. Got called out at 7AM to issues with email delivery. I've logged with Microsoft support & disabled Anti-Malware.
Marco M 11 Reputation points

2022-01-01T08:35:50.63+00:00

Thats what I did on all exchange systems - .\Disable-AntimalwareScanning.ps1 and restart Microsoft Exchange Transport.
After that all pending eMails were routed in the Mailboxes.

Thanks for your replys and happy new year.
Paul Lawrence 1 Reputation point

2022-01-01T09:24:30.86+00:00

Received the same error at around 3am GMT (United Kingdom). Fix was the same, disable anti malware policy.
asheroto 26 Reputation points

2022-01-01T10:18:41.29+00:00

Weird, same issue here, just started in the last day. No e-mails have been delivered since this error started.

Thanks for the path to disable antimalware scanning.
asheroto 26 Reputation points

2022-01-01T10:34:26.13+00:00

Looks like it's because they used a long variable type for the number which has a max integer value of 2,147,483,647, and the value in the error message 2201010003 ( 2,201,010,003 ) exceeds the max value.
asheroto 26 Reputation points

2022-01-01T10:36:13.39+00:00

With 32-bit... and Exchange is 32-bit... for now. :-)
Rizzo Andrea 1 Reputation point

2022-01-01T10:38:57.66+00:00

Hello, same issue mail flow freeze from 00:15 01.01 22
On all E2016 with last CU
Waiting on msexchange Team
WBR
Jay Drinkwater 1 Reputation point

2022-01-01T13:45:41.127+00:00

From https://learn.microsoft.com/en-us/cpp/cpp/integer-limits?view=msvc-170

LONG_MAX Maximum value for a variable of type long. 2147483647

Has the Y2K bug finally caught up with us?
pravin bedekar 6 Reputation points

2022-01-01T18:01:37.127+00:00

I also faced this issue and all mails are cleared after I disabled the Anti-Malware, but Mails are still getting delayed to end users, so kindly suggest
asheroto 26 Reputation points

2022-01-03T00:01:55.933+00:00

The fix has been released.
asheroto 26 Reputation points

2022-01-03T03:04:31.98+00:00

So I ran the PowerShell script, but still having issues! Same problem... What's weird is that event viewer does not report the error, but no e-mails will deliver. I restarted all services.

I then disabled anti-malware scanning again, restarted transport, and e-mails are flowing.

I also checked to ensure my engine date was as expected.... any ideas guys?

Answer 1

Maroiane Ghédira 31

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

0 comments

Answer 2

M L Leening 6

Exact the same error here,

The FIP-FS "Microsoft" Scan Engine failed to load. PID: 43256, Error Code: 0x80004005. Error Description: Can't convert "2201010003" to long.

Temporary disabled Antimalware scanning :
& $env:ExchangeInstallPath\Scripts\Disable-AntimalwareScanning.ps1

Started around 2:15 GMT+1 (Amsterdam)

0 comments

Answer 3

asheroto 26

The fix has been released. You can read about it here, link near bottom of article.

0 comments

Answer 4

Paul Christian 1

Had this issue on standalone Exchange 2016 servers, for two different clients

Disabling of malware scanning worked for me in both cases as well.

In both cases, email for those domains first flow through a third party spam/virus filter service. So I felt comfortable doing that. If you don't flow your email through such a scanning service you may want to try to seek other avenues for addressing.

0 comments

Answer 5

Samdi 46

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/

0 comments

Share via

Exchange Scan Engine failed to load - Can't convert "2201010003" to long

6 answers

Your answer