The popular email service Microsoft Exchange had a difficult start to the New Year when it was struck by a Y2K22 issue that stopped users from accessing their mailbox. People originally assumed it was their connection, but Microsoft immediately replied with an update after realizing it was the service all along.
According to The Verge, there have been concerns about the service, prompting some to doubt its utility, especially since the app shows no email. Microsoft Exchange losing its email operations and reflecting no messages in the inbox is a big business disaster.
Exchange administrators throughout the world realized that their servers were no longer transmitting email as the year 2022 rolled in and the clock struck midnight. They discovered that mail was becoming blocked in the queue after more investigation, and the Windows event log revealed one of the following errors:
These issues are caused by Microsoft Exchange attempting to save the data in a signed int32 variable when validating the version of the FIP-FS antivirus scanning engine.
“We’ve found a remedy to solve the problem of messages blocked in transport queues on Exchange Server 2016 and Exchange Server 2019 due to a latent date issue in a signature file used by the malware scanning engine within Exchange Server,” Microsoft states in a post on its support forums. When the problem arises, you’ll observe problems in the Exchange Server’s Application event log, notably events 5300 and 1106 (FIPFS)”.
Exchange Server 2016 and 2019 should be compatible with the new automated solution. Users’ reactions vary: some claim that the additional precautions are only effective after a server restart.
As the century neared, computer programmers realized that their software would perceive 00 as 1900 rather than 2000, a flaw that many thought would signal disaster for governments, businesses, banks, and industries throughout the world.
Many experts projected a global recession, and doomsday flyers warning of cataclysmic consequences from computer failures were widely distributed in the late 1990s.
Fortunately, the computer apocalypse never happened, with just minor interruptions reported, but the problem has resurfaced 22 years later, plaguing certain Microsoft Exchange servers.
For more information visit https://www.vebasystems.com/
