Quite a few Microsoft users reportedly experienced an Exchange Server bug at the start of the new year this year due to an inability by certain systems to process dates after the year 2021. The error, which affected Exchange Server 2016 and 2019, prevented many from being able to deliver email on Jan. 1. The messages were getting stuck in transport queues because the servers couldn’t process the year 2022.
What is Y2K22?
Answer: A Microsoft bug reminiscent of Y2K issues.
Shutterstock
Remember the whole Y2K thing in the ’90s, when people were afraid that computers wouldn’t be able to process dates after 1999? Well, apparently they should have been more concerned about that happening in 2022.
Quite a few Microsoft users reportedly experienced an Exchange Server bug at the start of the new year this year due to an inability by certain systems to process dates after the year 2021. The error, which affected Exchange Server 2016 and 2019, prevented many from being able to deliver email on Jan. 1. The messages were getting stuck in transport queues because the servers couldn’t process the year 2022.
Microsoft has since issued an automated fix, though in some cases it apparently didn’t work and had to be done manually instead (pour one out for those poor IT teams). Most affected organizations, though, were reportedly back up and running by Monday. Many have been referring to the incident as Y2K22.
Quite a few Microsoft users reportedly experienced an Exchange Server bug at the start of the new year this year due to an inability by certain systems to process dates after the year 2021. The error, which affected Exchange Server 2016 and 2019, prevented many from being able to deliver email on Jan. 1. The messages were getting stuck in transport queues because the servers couldn’t process the year 2022.
