Y2K22 (Exchange) - Contractor UK Bulletin Board

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Lance replied

5 January 2022, 17:35
bloody programmers
Leave a comment:
hobnob started a topic Y2K22 (Exchange)

2 January 2022, 10:44
Y2K22 (Exchange)

If you (or your client) use Exchange 2016/2019 on-prem, be aware of a problem that started yesterday morning:
Email Stuck in Transport Queues - Microsoft Tech Community
long wtf = 2201010001; on Twitter: "Dear @msexchangeteam. The FIP-FS “Microsoft” Scan Engine Failed to Load. Can’t Convert “2201010001” to long." / Twitter

Basically, the anti-malware scanner is checking the date/time of new signature files and comparing them to the current date/time (GMT/UST). More specifically, it uses "YYMMDDHHMM" format, then converts to a signed 32-bit integer (max value 2147483648). So, in Dec 2021, each number started with "2112..." which was fine. In Jan 2022, each number starts with "2201..." which is too big. In practical terms, that means that all incoming/outgoing email stopped flowing on the stroke of midnight between New Year's Eve and New Year's Day. Hence the nickname "Y2K22".

If a company has IT cover 24/7 then this has probably been resolved by now. However, if there are companies where all the staff left on Friday evening (31st), or even on Christmas Eve (24th) and will start back on Tuesday morning (4th), they're going to have a nasty problem when they arrive. Aside from the backlog, email will start bouncing back after 48 hours (i.e. tonight).
Tags: None

Working...

X