I never thought “The 2022 problemIt looks like the system administrator has been having problems since New Years’ Day.
Microsoft Due to a bug in Exchange Server, mail delivery will no longer be possible from January 1 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 was storing the year, month, day, etc. in decimal in this variable.
For example, December 31, 2021 will be 2,112.31x, xxx (information stored in the last 4 digits is unknown). This value does not exceed the maximum value above 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.
Error code: 0x80004005. Error Description: Could not convert “220100001” to long.
An error occurred and the Microsoft Exchange server that controls mail delivery did not function correctly.
Malware scan needs to be updated
As a countermeasure to this problem, MicrosoftSuggested update for malware scanning featureTo do.
The issue only occurred in the malware scanning engine called FIP-FS, and updating that engine version to “2112330001” will resolve the issue.
However, other programs can have similar problems, and as soon as they start working, more “The 2022 problem“It is also possible to be reported.
Source: Microsoft via BleepingComputer, The Verge