Description of the Root Management Server Unavailable alert
Could someone please explain to me how does the “Root Management Server Unavailable” rule work? There are few confusing things to me about this rule. First of all, I can find it under the Rules in the Authoring Pane of the Operations Console, configured as simple alerting rule. However, Alert gets automatically resolved (closed) by the System, which means that it actually behaves like two-state monitor. Second of all, when I look at the Properties of the rule, specifically at the data source configuration, it is configured to generate an Alert when the following event is found: Event Log: Operations Manager Event Source: Health Service Watcher Event ID: 271828 I cannot find any of such Alerts in the Operations Manager event log on the Root Management Server. I am not even able to enter the 6-digit Event ID in the filter properties to display only Event ID 271828 events. Still, I see Root Management Server Unavailable alerts being generated and closed in the past few days. Despite that, all else seem to work fine: alerting, notification subscriptions, reporting, health state calculation… and I cannot find any event in the event log to correlate with the unavailability of the RMS (SCOM 2007 R2). Any help is greatly appreciated, Vedran Matica
December 31st, 2009 1:01pm

Hi Vedran, this may be helpful http://it.peterspowerblog.com/2008/09/04/root-management-server-unavailable.aspx Otherwise I'm wondering if u need to delete the Health Service Store (C:\Program Files\System Center Operations Manager 2007\Health Service State\Health Service Store) (to do this stop the Health service, then rename the health service store to OLD and restart the Health Service) Let us know how you go.... John Bradshaw
Free Windows Admin Tool Kit Click here and download it now
December 31st, 2009 7:04pm

Hi John,Thanks for the feedback!The "MinutesToWaitBeforeAlerting" registry value was already configured before, but it didn't help us in resolving the issue.Second tip to delete the "Health Service Store" folder did the trick. We are no longer seeing "Root Management Server" alerts.However, I would still like to understand how does this monitor work. Could anyone explain me that?Thanks,Vedran
January 4th, 2010 11:40am

SCOM 2k7 R2 The root management server (HealthService) is running but has reported limited functionality soon after 9/2/2010 2:55:04 PM. The specific reason code is 43 and description is " System workflows essential to running of the product have failed to load. ". I have tried both of the solutions that Vedran suggested and it does not resolve my issue. Are there any other possible resolutions? My whole implementation was working fine for two weeks and now all of a sudden for no reasons with no changes, no snmp management (ever) and no third party additons, I get this same error.
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2010 10:12pm

We are also seeing this error. Everything seems to work fine and there are no event 271828 in the operations manager log. Can someone from MS explain how this monitor works as it does not seem to have anything to do with an event log ?
October 29th, 2010 11:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics