Exchange évènement FIPPS 5300 file d'attente des messages erreur
Starting year 2022, Microsoft Exchange Server users are facing problems with email messages delivery. All email messages are stuck in transport queues. Microsoft has acknowledged the issue and provided an official workaround to fix the issue.
Table of Contents
PROBLEM DESCRIPTION AND REASON:
Microsoft Exchange Servers are having an issue causing messages to be stuck in transport queues on Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change of the new year. Microsoft has mentioned that the issue is not a failure of the AV engine itself. This is not an issue with malware scanning or the malware engine, and it is not a security-related issue. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues.
The problem occurs due to a latent date issue in a signature file used by the malware scanning engine within Exchange Server. When the issue occurs, you’ll see errors in the Application event log on the Exchange Server, specifically event 5300 and 1106 (FIPFS), as shown below:
Log Name: Application
Source: FIPFS
Logged: 1/1/2022 1:03:42 AM
Event ID: 5300 or 1106
Level: Error
Computer: server1.contoso.com
Description: The FIP-FS “Microsoft” Scan Engine failed to load. PID: 23092, Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to long.
OR
The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unspecified error.
PROBLEM SOLUTION:
Microsoft has provided a temporary fix to resolve the issue immediately. You can implement the fix automatically using a scan engine reset script provided by Microsoft or manually using the steps given below. Whether you perform the steps automatically or manually, they must be performed on every Exchange 2016 and Exchange 2019 server in your organization. If you use the automated script, you can run it on multiple servers in parallel. Microsoft recommends starting with the servers in your environment that have the largest queues. You can use Get-Queue to view queue size and determine which queues are the largest.
A. AUTOMATED SOLUTION:
First download the script provided by Microsoft using following link:
Download Scan Engine Reset Script
Run the script on each Exchange server in your organization. You can run this script on multiple servers in parallel.