HealthService Availability Reports for Distributed Applications might be incorrect due to duplicate entries
HealthService Availability Reports for Distributed Applications might be incorrect due to duplicate entries in the HealthServiceOutage table. When the availability reports for the distributed applications are incorrect and are showing UP(Monitoring Unavailable) like this:
…whilst in Health Explorer the Apps looked healthy, then you might have a problem with duplicate entries in the HealthServiceOutage table.
To see if this is indeed the problem, please run the following query:
SELECT * FROM HealthServiceOutage HS1 JOIN HealthServiceOutage HS2 ON HS1.StartDateTime = HS2.StartDateTime
AND HS1.ManagedEntityRowId = HS2.ManagedEntityRowId WHERE HS2.EndDateTime IS NULL AND HS1.HealthServiceOutageRowId <> HS2.HealthServiceOutageRowId
In the OperationsManagerDW. If you find a NULL value in the EndDateTime column like this:
You have indeed the duplicate entries problem. This will be fixed in SP1 UR3. If you want a workaround, you can raise a support call at Microsoft. A Microsoft Support Engineer can provide a workaround in the meantime.
Thanks to Dirk van Coeverden (dirkv(at)microsoft.com)