- This topic has 1 reply, 1 voice, and was last updated 3 years, 4 months ago by
.
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
UK Tech Forums
› UKTH forums › 💻 Computers › 💬 Servers Et al › Remember the Y2K bug? Microsoft confirms new Exchange Y2K22 issue
UK Sentinel.As digital calendars around the world changed to 01.01.2022, Microsoft customers found their Exchange servers stopped processing emails.
Microsoft says it is aware of a programming flaw which saw some customers’ Exchange servers stop processing emails just as the clock struck midnight on New Year’s Eve.
System administrators, who are sharing workarounds on social media, have dubbed the bug Y2K22 – in the style of the Y2K bug which affected some computers at exactly the same time 22 years
Microsoft said its engineers had been “working around the clock on a fix” that wouldn’t require customers to fiddle with their on-premise servers to get things moving again, but warned they found this “would require several days to develop and deploy”.
Instead, those engineers are now working on a different update “which is in final test validation” that will require customer action, but also offer “the quickest time to resolution”.
Read more: https://news.sky.com/story/remember-the-y2k-bug-microsoft-confirms-new-y2k22-issue-12507401
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote
What actually went wrong?
The technical issue seems to lie with the way that Microsoft was naming updates for its malware-scanning engine, putting the year, month, and day (220101) at the front of another four-digit number (0001).
Microsoft seems to use this system because when an update is named “2,201,010,001” it is simple to mathematically check which update is the most recent as it will have the higher value.
In a completely sane world, madness is the only freedom (J.G.Ballard).
You need to login in order to vote