I never thought “The 2022 issueIt seems that the system administrator has been in trouble since New Year’s Day.
Microsoft Due to a bug in Exchange Server, mail delivery will not be possible from January 1st, and countermeasures are required.
Occurs because a signed 32-bit variable was used to store the date
This bug isMicrosoft On the Exchange Server programCaused by the type of variable used to store the date and how it was storedIt was done.
Exchange Server internally used a signed 32-bit variable type to hold date information.
The maximum value for this signed 32-bit is 2,147,483,647 (7FFFFFFF in hexadecimal).
And the Exchange Server stored the year, month, day, etc. in decimal in this variable.
For example, December 31, 2021 will be 2,112,31x, xxx (the information stored in the last 4 digits is unknown). This value does not exceed the above maximum value and there is no problem.
However,The first value in 2022 was 2,201,010,001, which exceeded the signed 32-bit range.。
For this reason,
Error: 0x8004005. Error Details: Unspecified Error.
or,
Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to long.
Error occurred, and the Microsoft Exchange Server that controls mail delivery did not work properly.
Malware scan needs to be updated
As a countermeasure to this problem, MicrosoftSuggested update of malware scanning functiondoing.
The problem occurred only in the malware scanning engine called FIP-FS, and updating the version of this engine to “2112330001” will solve the problem.
However, other programs may have similar problems, and as soon as they start working, more “The 2022 issue“Is also possible to be reported.
Source: Microsoft via BleepingComputer, The Verge
(Hauser)
