[BUG MICROSOFT EXCHANGE] Microsoft Exchange messaging was the victim of a bug during the transition to 2022, preventing any mail from being sent. The publisher has since published scripts to fix the problem, related to the integrated anti-virus.

BUG MICROSOFT EXCHANGE Microsoft Exchange messaging was the victim of

[BUG MICROSOFT EXCHANGE] Microsoft Exchange messaging was the victim of a bug during the transition to 2022, preventing any mail from being sent. The publisher has since published scripts to fix the problem, related to the integrated anti-virus.

Would 2022 be a bug year, as many had feared for the transition to the year 2000? While some are worried about the arrival of version 100 of Google Chrome which could cause problems on some websites, Microsoft has already borne the brunt of a first malfunction that has caused fear among many business users. In fact, as reported Bleeping Computer, from the transition to the new year, the 1er January 2022 at midnight, the Exchange mail servers blocked the sending of mails. The incident, initially inexplicable, caused panic among system administrators who saw multiple error messages in the event log, such as “Failed to initialize the FIP-FS scan process. Error: 0x8004005. Error details: Unspecified error” Where “Error code: 0x80004005. Error description: Could not convert 220100001 to long.” In short, a cold sweat to start the year off right …

Called Y2K22, the problem did not come from their settings, but quite simply from the anti-virus integrated into the messaging system, or, more exactly from its scanning engine, as Microsoft explained in a post published on his Tech Community forum. “The problem is related to a failure of the date verification with the change of the new year and is not a failure of the anti-virus engine itself. The version check performed against the signature file does crash the malware engine, causing messages to hang in transport queues “, details the editor.

If the system administrators had to fend for themselves for a few hours, Microsoft quickly looked into the matter by indicating two ways to solve the problem, with scripts, one manual, the other automatic. The editor specifies however that it will probably be necessary to wait a little before everything returns to the order, the time for all the messages blocked in queues to be processed. In short, more fear than harm in the end, but a bad surprise to start the new year …

ccn3