We periodically will start getting this exception in the BizTalk Admin Console and it’s annoying to say the least. Previously, we would do a reboot not really knowing what was causing the problem. Well, the solution from this article worked for us. All we had to do was restart the Windows Management Instrumentation service and it started working again.
Still not sure what creates this condition, but this fix is easier than taking a production server down to reboot!