Finding the reason behind this never ending discovery process could take some time. Mostly it turned out that the SQL Broker Service wasn’t running. And this service is needed for the discovery of servers/clients.
In SCOM R2 Microsoft has addressed this issue. Yes, the SQL Broker Service still needs to be in a running state but now the wizard shows this screen:
So when a discovery keeps running on with no end, one now knows what it can cause. Of course there might be another reason for it but more than 90% of the time, the SQL Broker Service – not running - is the culprit.
Even though it is nothing more than a small cosmetically change, it can be a real timesaver for troubleshooting.
No comments:
Post a Comment