This message was deleted.

Yes, I had the same error at a customer. I did the DBA stuff, disabling a couple of pagelocks on indexes in the chb_state_workers like the article mentions but this did not solve the error in the site check. The article notes "For smaller sites or light user load we won’t see any issues (except the site test failure)" and "if the site is large and/or under load then we might start". It's so not us with 90 max concurrent users for that customer, so we decided to go ahead with the upgrade and worry about it when we actually see those problems mentioned. The upgrade went fine and we didn't have the problems mentioned in the article afterward. YMMV of course 🙂 .