The Microsoft Exchange server was unable to correctly parse the new date of 2022, resulting in a problem of inability to process emails, which was ridiculed by users as “the 2022 version of the millennium bug”.

Microsoft releases a fix to solve the “2000 version of the millennium bug” problem on Exchange servers

FIP-FS scan engine failed to load-unable to convert “2201010001” to long (2022/01/01 00:00 UTC)

According to a report released by Marius Sandbu, manager of the Norwegian company Sopra Steria, because Microsoft uses signed int32 as the date format, 2201010001 exceeds the maximum value of long int of 2147483647.

(“Millennium bug” means that because some computer programs only use two decimal digits to represent the year, errors will occur when they cross the century.)

Microsoft has now released a fix for this problem, which can be executed through an automated script.

This issue affects Exchange Server 2013, 2016, and 2019.

The Links:   LC104S1-A1 EL512256-H2