Exchange Year 2022 Problem: FIP-FS Scan Engine failed to load – Can’t Convert “2201010001” to long (2022/01/01 00:00 UTC) - ALL Mail-Flow Affected!
​
​Microsoft released a patch for the Exchange 2013/2016/2019 FIP-FS Scan Engine that has broken most on-prem Exchange servers as of this past midnight on 1/1/2022. IT Admins everywhere were scrambling as they could not load the FIP-FS scan engine (virus scanner) and report an error Can't Convert "2201010001" to long. You are probably not alone, as of Jan. 1, 2022 0:00 UTC on-premises Exchange servers seem to freezing transport of all emails – a date can't get converted.
​
​Here is a quick overview of what is going on & how to fix this ASAP.
​
​***FIP-FS Scan Engine:FIP-FS is probably the anti-malware virus scanner that has been on board since Exchange Server 2013. This is supposed to scan the on-premises Exchange Server installation for malicious content. However, this anti-malware scan engine seems to cause problems more often. 
​
​The exchange server was stuck with this error: The FIP-FS "Microsoft" Scan Engine failed to load. PID: 39268, Error Code: 0x80004005. Error Description: Can't convert "2201010003" to long. / Event ID 5300
​
​***THE FIX:

1 - Exchange Shell - "Set-MalwareFilteringServer  -BypassFiltering $true"
2 - Restart the MSExchange Transport service
3 - Exchange Shell - "Get-ExchangeServer | Get-Queue " to verify that they are flushing out the stuck emails

And email is going again...FYI happy new year Exchange!
​
​So it seems that some (all?) Exchange servers are affected.
​
​Be on the lookout for any on-prem Exchange servers as you could be affected right now.
​
​We're here if you have any questions on this at all.