If you woke up on January 1, 2022 and found that your business email inbox was unusually empty, you are not alone. Microsoft started the new year with a bug that prevented Exchange servers from sending e-mail, but luckily a fix has since been released, as described in a report by Beeping computer.
“The problem relates to a bug in the date check at the turn of the year and is not a bug in the AV engine itself,” explains Microsoft in a post on his tech community forum. “The version check performed against the signature file causes the malware engine to crash, causing messages to get stuck in transport queues.”
Microsoft outlines the solution to the problem in its post and urges administrators to either implement the fix manually or apply an automated script. The post also contains a detailed FAQ, which states that the implementation of the solution “will take some time” before administrators are implemented. And depending on how many e-mails are in the queue, it can take a while for the messages to land in the inboxes of the intended recipients.
Problems started at midnight on January 1st, with an Exchange administrator on Reddit draw attention to the problem. As explained by Beeping computer, administrators noticed error messages in the Exchange server event log, such as: B. “The FIP-FS scan process failed to initialize. Error: 0x8004005. Error details: Unknown error “or” Error code: 0x80004005. Error description: “2201010001” cannot be converted to long. ”
Administrators have been forced to find alternative solutions during the time it took Microsoft to fix the issue, but now that the company has released an official fix, it looks like the Y2K22 crisis is over.