Hi,I receive lots of the following alerts (for different servers) from SCOM 2007 but nothing from MOM 2005.Alert: Health Service Heartbeat Failure Path: Microsoft.SystemCenter.AgentWatchersGroupWhat does it mean and how do I know if these are real alerts (positive not false alerts?Thank,Ziba

Good Morning, could someone help me with this request. Every afternoon, I receive lots of alerts with subject "Health Service Heartbeat Failure; Microsoft.SystemCenter.AgentWatchersGroup" for different servers. Thanks, Ziba

Heartbeat failure simply means the agent is not sending heartbeats to the management server - or there is a serious health problem with the management server. You should check the agent OpsMgr event log to see if it is losing connectivity to the agent - or if the healthservice is stopping

Thank you Kevin again for your great help and feed backs. My question is, how to tell if it's the management server or it's issue with the managed servers? In MOM 2005, we could say that by looking at the last contacted heartbeat from Admin Console. We don't have that in SCOM. Ziba

In the alert - in the alert description - it will tell you what computer is the problem: "The Health Service on computer DC8.opsmgr.net failed to heartbeat."As to "last contacted" - I know - totally agree - we need this back. It was a wonderful way for an administrator to see the order of machines and their last contact to the management server. I discuss this a little bit here:http://blogs.technet.com/kevinholman/archive/2008/06/27/which-servers-are-down-in-my-company-and-which-just-have-a-heartbeat-failure-right-now.aspxMarius discusses the "last contacted" issue here: http://blogs.msdn.com/mariussutara/archive/2008/07/28/last-contacted-better-sql-query.aspxNeither are perfect solutions....

Thank you Kevin, the view would work better for me since we have other tools which help us identify the down servers. Ziba

Hi Guys, In my case heartbeat was getting failed in perticular time and there were flood of email notifications as well, after checking all the possible couse i found that it was SQL Collation issue it was not set to SQL_Latin1_General_CP1_CI_AS, after moving the DB's to new instance with correct collation issue got fixed.