If you’ve answered yes to these questions, you’ve most certainly looked for the fix, and found other users in the same boat. They try and try to fix the issue with adjustments in official documentation or otherwise, with no results.

So, as suggested, I added a 2nd vCPU to my exchange server (running on Windows Server 2008 x64, in a vSphere cluster), and started it up. These specific warning messages in my event log went away completely. Okay, after several weeks of monitoring, I may have had a couple of warnings here and there. But that’s it. No longer the hundreds of warnings every day.

As for the official explanation, I don’t have one. Adding vCPU’s to fix problems is not something I want to get in the habit of, but it was an interesting problem, with an interesting solution that was worth sharing.