Start United States dc3 United States software in english pdf Microsoft releases official fix for Y2K22 Exchange Server bug that was causing...

Microsoft releases official fix for Y2K22 Exchange Server bug that was causing mail jam

335
0
TEILEN

News, Reviews & Betas which includes large community peer support Microsoft has delivered on its promise of releasing a solution, both automated and manual, for the Y2K22 Exchange Server bug that was causing mail and messages to get stuck in transport queues.
System administrators looking over Microsoft Exchange servers probably haven’t had the most joyous start to their new years. That’s because there has been a massive date processing failure issue as the new value chosen „2.201.010.001“ exceeds what the Servers are capable of processing under the current Int32 data type. As a result, the malware checking engine is crashing, and consequently, emails and messages have been stuck in transport queues across Exchange Servers 2016 and 2019 with Application event log errors 5300 and 1106 (FIPFS). Microsoft said that it was aware of the problem and was working on a fix. The company has kept its promise and has released a resolution for the problem. It has provided both an automated scan engine reset script solution as well as a manual input solution. First, we have the automated scan engine reset script (available at https://aka.ms/ResetScanEngineVersion). It can be run parallelly across multiple servers. The successful script completion should give the following output: Next up, steps for the manual fix are provided for those who prefer to do a manual restore. You may find more details on the official Microsoft blog post linked here.