on January 1, 2022 Microsoft Exchange An error has occurred on the e-mail servers. Due to the error, many people had problems accessing their email account. The company released a patch for the solution after the incident occurred.
Microsoft Exchange, one of the most preferred e-mail services, entered the new year with a critical error. In a report by Bleeping Computer, Microsoft Exchange’s FIP-FS It was explained that it was caused by the antivirus engine. The problem that arose due to the variable in which numbers are saved in the FIP-FS version control system has affected millions of users.
Important Microsoft Teams warning to users from Google
Google warned users that emergency calls may not be possible due to the Microsoft Teams application. He also gave the solution.
Microsoft Exchange servers crashed due to date error
Microsoft’s Tech Community “The issue is with a date check error with the new year changing. It’s not an error in the FIP-FIS antivirus engine itself. Version checking against the signature file causes the malware engine to crash, causing messages to get stuck in transport queues.” statements are included.
Sharing the solution to the problem, the company explained that administrators can perform the fix manually or automatically. It is stated that it will take some time to implement the solution on the solution page, which also includes the detailed FAQ (Frequently Asked Questions) text.
An Exchange administrator who shared on Reddit stated that he realized the situation on New Year’s Eve. In Exchange’s log files, “Failed to start FIP-FS Scan. Error: 0x8004005. Error Details: Unspecified Error” or “Error Code: 0x80004005. Error Description: Cannot convert “2201010001” to long.” The managers, who stated that they encountered one of their mistakes, underlined that they had to find an alternative solution.