Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/dev.phoenixs.co.uk/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-table-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/dev.phoenixs.co.uk/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-table-builder-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/dev.phoenixs.co.uk/wp-includes/functions.php on line 6121
Microsoft Exchange 2016/2019 Y2K22 bug - Phoenix Software
Contact

Deprecated: Function get_the_author was called with an argument that is deprecated since version 2.1.0 with no alternative available. in /var/www/dev.phoenixs.co.uk/wp-includes/functions.php on line 6121

Microsoft Exchange 2016/2019 Y2K22 bug

Ben Murden

January 4th, 2022

Microsoft customers are experiencing an issue that is causing messages to be stuck in transport queues on Exchange Server 2016 and Exchange Server 2019.

The problem – which started at 00:00 on 01.02.2022 – has been triggered by a date check failure created by the change of a new year from 2021 to 2022 and is not a failure of the AV engine itself.

Microsoft has confirmed that it is not an issue with malware scanning or the malware engine, and it is not security related. The version checking performed against the signature file is resulting in the malware engine crashing, resulting in messages getting stuck in transport queues.

Microsoft has released a workaround, which can be found within its Tech Community pages.

For support or assistance with this on-going issue, contact us.