Site icon Real Mi Central

Microsoft releases FIP-FS Y2K22 vulnerability fixes that cause Exchange server failure

Microsoft

Microsoft

Just before New Year’s Eve the day before yesterday, Microsoft Exchange users were affected by a 2022 bug that prevented the sending of emails. The 2022 date removed error in the FIP-FS anti-malware scanner caused the system to prompt the FIP-FS scanning process to fail to initialize.

This error caused many system administrators to stop New Year’s Eve celebrations abruptly, and Microsoft also did it during the holidays. No idle time, an official fix was released for this problem in just two days. Anyone who encounters the problem can apply the fix manually or use an automated script to handle the failure.

join us on telegram

Microsoft said in its support forum post: We have created a solution to solve the problem of messages stuck in the transmission queue on Exchange Server 2016 and Exchange Server 2019 because the malware scanning engine in Exchange Server uses There is a potential date issue in the signature file. When the issue occurs, you will see errors in the application event log on the Exchange server, especially events 5300 and 1106 (FIPFS).

The company stated that users can visit https://aka.ms/ResetScanEngineVersion to apply a fix, or they can use a manual option instead.

Microsoft Explained.

Instead of using scripts, customers can also manually perform steps to solve the problem and restore service. To manually resolve this issue, you must perform the following steps on each Exchange server in your organization.

Delete existing engine and metadata

Update to the latest engine

Verification engine update information

After updating the engine, it is also recommended to verify whether the mail flow is normal and whether there are FIPFS error events in the application event log.

Exit mobile version