tag:dreamwidth.org,2009-04-14:58489 Monica Monica 2022-01-03T05:09:02Z tag:dreamwidth.org,2009-04-14:58489:2107710 2022-01-03T05:09:02Z 2022-01-03T05:09:02Z public 0 <p>We all got through the anticlimactic Y2K bug 22 years ago, and the next digital calendar crisis isn't expected until 2038 (Unix epoch), but... <a href="https://www.theverge.com/2022/1/2/22863950/microsoft-exchange-y2k22-bug">apparently Microsoft Exchange has a Y2k22 bug</a>, which prevents email from being delivered until sysadmins apply a manual fix. Just what they wanted to hear on a holiday weekend.</p> <p>Apparently Exchange is using a funny string representation of dates and then trying to convert that string to a numeric format, and with the bump in year it now doesn't fit into a long. Really, I'm not making this up. Why they don't use standard date formatting, I don't know. I don't know much about how Exchange is put together.</p> <p>This linked <a href="https://www.reddit.com/r/sysadmin/comments/rt91z6/exchange_2019_antimalware_bad_update/">Reddit post</a>, which has had several updates, includes this:</p> <blockquote> <p>Interestingly, this fix includes a change to the format of the problematic update version number; the version number now starts with “21” again, to stay within the limits of the ‘long’ data type, for example: “2112330001”. So, Happy December 33, 2021!</p> </blockquote> <br /><br /><img src="https://www.dreamwidth.org/tools/commentcount?user=cellio&ditemid=2107710" width="30" height="12" alt="comment count unavailable" style="vertical-align: middle;"/> comments