Last Updated on 02/01/2022 by Sanskriti
Microsoft has stated that it is aware of an issue that is causing Exchange Servers to go down throughout the world. The error “FIP-FS Scan Engine failed to load—Can’t Convert “2201010001” too long (2022/01/01 00:00 UTC)” has been reported by several users.
The problem, which users believe is caused by the “220101001” update, appears to have crippled Microsoft’s Filtering Management Service” since it is unable to accommodate the new date format.
Marius Sandbu, main tech lead of Sopra Steria in Norway, remarked, “The reason for this is because Microsoft is using a signed int32 for the date and with the new value of 2.201.010.001 is over the max value of the “long” int being 2.147.483.647. This seems to be affecting Exchange versions 2016/2019,”
Microsoft has recognized the problem with a post on their help website that reads:
“We are aware of and working on an issue causing messages to be stuck in transport queues on Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change of the new year and it not a failure of the AV engine itself. This is not an issue with malware scanning or the malware engine, and it is not a security-related issue. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues.”
The problem originates from Microsoft’s update naming strategy, which places the year, month, and date in front of the update number. In this scenario, “220101” and “0001” are the updated numbers.
The issue is that this field appears to have a 31-bit restriction, which implies the highest value is 2 to the 31st power, or 2147483648. As a result, the date check failed when the calendar turned to 2022.
