<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>OpsMgr 2007: Cluster shows as not monitored under cluster state</title><link>http://blogs.technet.com/operationsmgr/archive/2008/11/06/opsmgr-2007-cluster-shows-as-not-monitored-under-cluster-state.aspx</link><description>Every once in a while we run across an issue where the cluster state view in System Center Operations Manager 2007 may show a cluster as not monitored.&amp;#160; If you happen to run into this too then here are 4 steps sent to me by Adrian Doyle that should</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>OpsMgr 2007: Cluster shows as not monitored under cluster state | MS Tech News</title><link>http://blogs.technet.com/operationsmgr/archive/2008/11/06/opsmgr-2007-cluster-shows-as-not-monitored-under-cluster-state.aspx#3148494</link><pubDate>Thu, 06 Nov 2008 16:36:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3148494</guid><dc:creator>OpsMgr 2007: Cluster shows as not monitored under cluster state | MS Tech News</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://mstechnews.info/2008/11/opsmgr-2007-cluster-shows-as-not-monitored-under-cluster-state/"&gt;http://mstechnews.info/2008/11/opsmgr-2007-cluster-shows-as-not-monitored-under-cluster-state/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: OpsMgr 2007: Cluster shows as not monitored under cluster state</title><link>http://blogs.technet.com/operationsmgr/archive/2008/11/06/opsmgr-2007-cluster-shows-as-not-monitored-under-cluster-state.aspx#3164417</link><pubDate>Fri, 05 Dec 2008 20:02:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3164417</guid><dc:creator>mkielman</dc:creator><description>&lt;p&gt;Based on the above, it appears that I should remove the trailing space after 'W: '. Is this correct?&lt;/p&gt;
&lt;p&gt;Discovery data couldn't be inserted to the database. This could have happened because &amp;nbsp;of one of the following reasons:&lt;/p&gt;
&lt;p&gt; 	- Discovery data is stale. The discovery data is generated by an MP recently deleted.&lt;/p&gt;
&lt;p&gt; 	- Database connectivity problems or database running out of space.&lt;/p&gt;
&lt;p&gt; 	- Discovery data received is not valid.&lt;/p&gt;
&lt;p&gt; The following details should help to further diagnose:&lt;/p&gt;
&lt;p&gt; DiscoveryId: 5d7e65f8-968f-d501-320b-b26720a22b9a&lt;/p&gt;
&lt;p&gt; HealthServiceId: ee42b893-f15c-4f73-1d0d-f5977dd612ca&lt;/p&gt;
&lt;p&gt; Invalid relationship target specified in the discovery data item.&lt;/p&gt;
&lt;p&gt;RelationshipTargetBaseManagedEntityId: b5c16d1e-3e9d-3ec0-04ab-61245b3cdaad&lt;/p&gt;
&lt;p&gt;RuleId: 5d7e65f8-968f-d501-320b-b26720a22b9a&lt;/p&gt;
&lt;p&gt;Instance:&lt;/p&gt;
&lt;p&gt;&amp;lt;?xml version=&amp;quot;1.0&amp;quot; encoding=&amp;quot;utf-16&amp;quot;?&amp;gt;&amp;lt;RelationshipInstance TypeId=&amp;quot;{524c7317-9a1c-a525-3d1c-acc7c2ff2200}&amp;quot; SourceTypeId=&amp;quot;{e761abda-c410-9852-be05-d859560e6efa}&amp;quot; TargetTypeId=&amp;quot;{f1ce5d3a-f8ab-1ae2-b5d7-94d999320673}&amp;quot;&amp;gt;&amp;lt;Settings /&amp;gt;&amp;lt;SourceRole&amp;gt;&amp;lt;Settings&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{5C324096-D928-76DB-E9E7-E629DCC261B1}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;sdsqla.corp.dom&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{C0D1A296-F98A-2580-3BE8-BFC1A4F22B33}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;SDSQLCL1&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{5A481B0E-7A61-A639-CF28-B41CF019432F}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;sdsqla&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{CA7F145F-328F-CFC7-2FCD-B5A886AEB4C5}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;SQL DEVA&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;/Settings&amp;gt;&amp;lt;/SourceRole&amp;gt;&amp;lt;TargetRole&amp;gt;&amp;lt;Settings&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{5C324096-D928-76DB-E9E7-E629DCC261B1}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;sdsqla.corp.dom&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{C0D1A296-F98A-2580-3BE8-BFC1A4F22B33}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;SDSQLCL1&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{5A481B0E-7A61-A639-CF28-B41CF019432F}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;sdsqla&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{CA7F145F-328F-CFC7-2FCD-B5A886AEB4C5}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;SQL DEVA&amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;Setting&amp;gt;&amp;lt;Name&amp;gt;{2E0D225D-25BB-F33F-6031-FF09758505B5}&amp;lt;/Name&amp;gt;&amp;lt;Value&amp;gt;Disk W: &amp;lt;/Value&amp;gt;&amp;lt;/Setting&amp;gt;&amp;lt;/Settings&amp;gt;&amp;lt;/TargetRole&amp;gt;&amp;lt;/RelationshipInstance&amp;gt;.&lt;/p&gt;
</description></item></channel></rss>