They said that the fix will be applied in patch 6.01 - it requires an update to our client software, and they opted not to roll it out early and risk breaking something else since there's additional code already in there that hasn't been fully QA'd yet.

So after next Monday evening, if you are still getting 2002, then something else is going on beyond their hoped for fix. We have to wait and see.