How to Fix Y2K22 issue in Microsoft for Exchange ?

January 04, 2022

How to Fix Y2K22 issue in Microsoft for Exchange ?

Microsoft has given a fix for the Y2K22 bug that stopped up Exchange servers with undelivered messages on January first.

An issue with naming show of updates Microsoft issues to Exchange accidentally broke usefulness. Clearly, the manner in which Microsoft dates refreshes (Year/Month/Day design) didn't consider that it had a self-assertive constraint of 2147483647.

Thus, when the update named 220101001 was sent, it overshot the breaking point and bombed date checks. This impacted Exchange adaptations 2016 and 2019.

"The issue connects with a date check disappointment with the difference in the new year and it's anything but a disappointment of the AV motor itself. This isn't an issue with malware checking or the malware motor, and it's anything but a security-related issue," Microsoft had said already, talking on the issue.

A fix has now been conveyed by the organization, which can either be physically applied or utilizing an autorun script that will do as such naturally.

"We've made an answer for address the issue of messages trapped in transport lines on Exchange Server 2016 and Exchange Server 2019," said Microsoft on its backing page.

"In light of an idle date issue in a mark record utilized by the malware filtering motor inside Exchange Server. At the point when the issue happens, you'll see mistakes in the Application occasion sign on the Exchange Server, explicitly occasion 5300 and 1106 (FIPFS)".

: TCL 20 Pro 5G Unlocked Android Smartphone with 6.67” AMOLED FHD+ Display, 48MP OIS Quad Rear Camera System, 6GB+256GB, 4500mAh Battery with Wireless Charging, US 5G Version Cellphone, Marine Blue