Microsoft confirms bug with
Exchange 2022 FIP-FS scan engine
Many Microsoft Exchange users were faced with a worrisome issue on 1st January (00:00 UTC) when their mail was suddenly unable to send. Since the start of the New Year, messages would be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. This error specifically affected events 5300 and 1106 (FIPFS) and would show an error message ending in one of the notes below:
“Description: The FIP-FS “Microsoft” Scan Engine failed to load. PID: 23092, Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to long.”
“Description: The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unspecified error.”
Microsoft have confirmed that this problem is due to a date error in the signature file used by the malware scanning engine within the Exchange Server. To rectify this ongoing issue, Microsoft have announced a solution which requires customer action to complete the necessary fix.
Click here for official step-by-step instructions on how to fix this issue, or contact our IT team if you need a little more assistance.
Blog Top Picks
Have you prepared for BT’s Big Switch Off of PSTN?
By the end of 2025, BT will switch off all PSTN line and your phone system will go off. By this time, you must have a VoIP system or you will no longer be able to take or make calls. Don’t wait!
Map of Worldwide Ransomware Attacks
Discover the latest ransomware attacks worldwide, updated daily, since 2018. Ransom amount, if the ransom was paid, the entity, sector and industry that was targeted, and the strain of ransomware used, is all data that is visible where available.