Microsoft releases fix for Exchange bug Y2K22 that was shutting down company emails


If you’ve woken up on January 1, 2022 and found your work email inbox to be unusually empty, you’re not alone. Microsoft rang the New Years with a bug that prevents Exchange servers from sending emails, but luckily a fix has since been released, as detailed in a report by Beeping computer.

“The problem is related to a failure of the date verification with the New Year change and is not a failure of the AV motor itself,” Microsoft explains 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 hang in transport queues.” “

Microsoft describes the solution to the problem in its article, requiring administrators to implement the fix manually or to apply an automated script. The post also contains a detailed FAQ, noting that the solution “will take some time” for admins to implement. And depending on the number of emails stuck in the queue, it may take some time for messages to land in the inboxes of their recipients.

The problems began to crop up at midnight on January 1, with an Exchange administrator on Reddit draw attention to the problem. As explained by Beeping computer, administrators started noticing error messages in the Exchange Server event log, such as “Failed to initialize the FIP-FS scan process. Error: 0x8004005. Error Details: Unspecified Error “or” Error Code: 0x80004005. Error Description: Could not convert “220100001” to long. ”

Admins were forced to come up with workarounds during the time it took Microsoft to fix the issue, but now that the company has released an official patch, it looks like the Year 2000 crisis is over.

Source link


About Author

Comments are closed.