New Delhi: Microsoft Exchange didn’t start the new year well, as its popular email service was hit by a Y2K22 bug that prevented users from accessing their inboxes. People initially thought it was their connection, but eventually realized that their service was affected, and Microsoft quickly discovered a fix.
The Verge reported that there were complaints about the service that led people to question its use, especially when it didn’t show any matches in the app. It’s a big corporate mess to see Microsoft Exchange losing its email functions and no mail showing up in the inbox.
read also
Just at midnight early 2022, Exchange administrators around the world discovered that their servers were no longer distributing email. On investigation, it was found that Mail is trapped in the queue. The errors are caused by Microsoft Exchange checking the version of the FIP-FS antivirus scanning engine and trying to store the date in a signed int32 variable.
In a post on its support forums, Microsoft states, “We have created a bug fix to address the issue of mail stuck in the transport queue on Exchange Server 2016 and Exchange Server 2019 because the sign file used by the malware contains a Hidden date is the problem. When a problem occurs with the scanning engine inside Exchange Server, you will see faults in the Application event log on the Exchange server, specifically events 5300 and 1106.”
Microsoft’s system admins have dubbed the glitch Y2K22 in reference to the Y2K bug, a computer programming problem that affected some computers 22 years ago.