Status of service from Operations Manager - NotRunnig, but really this service is started
Good day! We have a CCR cluster (geo cluster, nodes in different subnets). System Attendant Service Monitor in Critical state, service NotRunnig. This monitor are used for monitoring MSExchangeSA service on active node. But really this service is started and worked on active node. I make restart MSExchangeSA service on active node, but this does not help me. How can I debug this case?
December 23rd, 2010 4:12am

Hi Valery, This can happen on occasions with monitors unfortunately, which I have explained in more detail here: http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/74eb6293-9e5c-4d9a-8493-c81cdce5b4a1 I would recommend trying each step below to see if they fix the issue: 1) Try using the Recalculate Health option for the monitor in Health Explorer, this might fix the health state 2) Apply a maintenance to this monitor for 5-10 minutes, when the monitor comes out of maintenance it will be forced to re-assess it's health state 3) Flush the agent's cache on the active node (Stop the HealthService service, delete the folder '%SystemDrive%\Program Files\System Center Operations Manager 2007\Health Service State', start the HealthService service). This will force the agent to re-assess all health state, and update it's config for all monitored objects 4) Flush the agent's cache on the passive node (same instructions as step 3) Let us know how you go with this issue. Cheers, Brian
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2010 3:11pm

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

Other recent topics Other recent topics