Hi, I have a SCOM environment that has been up and running for a long time. Now I have encountered some problems. If I go into Administration -> Management Server, the RMS server is gray. If I go in to Monitoring -> Health Service Watcher State, all agents are gray. If I go in to any agent and go into the Health Explorer, I will see that Availability is gray. If I attempts to reset health on it, I'm getting the following error message: "Health Explorer Could not reset the monitor". For all agents, there is now this message in Event log: eventID 21024: "OpsMgr's configuration may be out-of-date for management group MANAGEMENTGROUP, and has requested updated configuration from the Configuration Service. The current(out-of-date) state cookie is "XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX" On my RMS I find this errors: eventID 1102: Rule/Monitor "Microsoft.Windows.DNSServer.Library.Depends.DomainSecurityDependsOnZoneSecurity" running for instance "<DOMAIN>" with id:"{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXX-XXXXXX}" cannot be initialized and will not be loaded. Management group "<MANAGEMENT GROUP>" eventID 10801: Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons: - Discovery data is stale. The discovery data is generated by an MP recently deleted. - Database connectivity problems or database running out of space. - Discovery data received is not valid. eventID 26319: An exception was thrown while processing SubmitTasks for session id uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx;id=5. Exception Message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.LocationMonitoringObjectNotAvailableException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.LocationMonitoringObjectNotAvailableException: Health Service '<RMS-SERVERNAME>' in which the location monitoring object is contained is not available. Make sure that the computer hosting the Health Service is available and verify that the Health Service is running.). Please help me.

Hey Tobbe. Have you verified that all the OpsMgr services is running on your RMS? And like the 10801 event suggests, that your OperationsManager database is full?mats.w | www.opsmode.com

Yes, I have checked both that. I have also tried to reboot the RMS, but it's still the same problem.

Can you comunicate with the db server? ie telnet on port 1433 or the port your SQL listens on.. How much free space do you have in the db?mats.w | www.opsmode.com

Hi Tobbe, Please try the following method and see if it helps: RMS grayed out and server discovery failed http://scug.be/blogs/scom/archive/2009/02/11/rms-grayed-out-and-server-discovery-failed.aspx Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I tried it and it was no problem to reach myy db-server on port 1433. It's alot of free space on my DB.

Thank you, but the time was correct for my servers, so this weren't my problem.

The problem is now solved. I solved it by stopping all systems center services on the RMS server, and then I changed the name of the folder: \System Center Operations Manager 2007\Health Service State\. After that, it works again.