On some of our Windows 2012 R2 servers running SQL 2008 R2, we get false alarms saying that some SQL services have stopped, when they are still running.

Example:

Source	servername
Severity	Service Went Down
Last Updated	2015/10/02 03:50:09 PM BST
Message	Windows NT Service SQL Server Reporting Services (MSSQLSERVER) is Down

This example server had no other alerts, and there are no events showing that the service went down.

Running an "update status" does not refresh the alert, i.e. it still is reporting the service as down.

Is there some way to avoid these false alerts? We are running OpManager build 11600.

Thanks,

Nick