SQL MP Reporting Services Discovery Issue

• Question

• 

  

  0

  Sign in to vote

  I'm finding that not all of my SSRS 2005 and 2008 R2 instances are being discovered by the latest SQL Server MP (v6.1.314.35).  Appearingly, it's only when SSRS is installed in a scaleout configuration with the database on a remote SQL server.  SSRS instances installed on the same server as the SQL database engine are discovered correctly.  (All use the default instance name.)
  
  There are no errors or warnings in the Operations Manager event log on the SSRS servers, and I've verified that manually running the discovery script produces what appears to be correct output. 
  
  I do see the following 10801 event ID (reformatted for clarity) on my Operations Manager 2007 R2 (CU3) management server.  (And neither has the MP been deleted nor are there database connectivity/space issues.)
  
  ---------------------------------
  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.
  
   The following details should help to further diagnose:
  
   DiscoveryId: 4cc14cc2-e918-1733-726a-32631502c25b
   HealthServiceId: 39535231-54bc-bb80-18ea-cac9397ec383
   Unable to resolve the monitoring class property name specified in the discovery data item. Try using a fully qualified name.
  MonitoringClassPropertyName: {02392F7E-2262-C4CE-088F-70C3C6D7372C}
  RuleId: 4cc14cc2-e918-1733-726a-32631502c25b
  Instance:
  <?xml version="1.0" encoding="utf-16"?>
  <ClassInstance TypeId="{6ec5d340-9715-ef07-3df6-dcd77b75f2b9}">
  <Settings>
  
  <Setting>
  <Name>{5C324096-D928-76DB-E9E7-E629DCC261B1}</Name>
  <Value>[appropriate SSRS server FQDN]</Value>
  </Setting>
  
  <Setting>
  <Name>{0F700489-D513-FC14-2FE1-B514BC789F42}</Name>
  <Value>MSSQLSERVER</Value>
  </Setting>
  
  <Setting>
  <Name>{0726CA99-DAF6-9536-D735-F0EC744C822F}</Name>
  <Value>ReportServer</Value>
  </Setting>
  
  <Setting>
  <Name>{02392F7E-2262-C4CE-088F-70C3C6D7372C}</Name>
  <Value>REPORTING SERVICES</Value>
  </Setting>
  
  <Setting>
  <Name>{1F95F749-FC77-0997-98D1-EE792FD862E2}</Name>
  <Value>9.4.5000</Value>
  </Setting>
  
  <Setting>
  <Name>{7998558D-6F5D-4EB7-11DE-A539952ED91F}</Name>
  <Value>4</Value>
  </Setting>
  
  <Setting>
  <Name>{1931C6FE-E7EF-05C6-9D51-23CE1E903D54}</Name>
  <Value>Standard Edition (64-bit)</Value>
  </Setting>
  
  <Setting>
  <Name>{22410AD7-B63C-A712-6E7C-DC52B6428EA0}</Name>
  <Value>c:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\</Value>
  </Setting>
  
  </Settings>
  </ClassInstance>.
  ---------------------------------
  
  
  The GUID {02392F7E-2262-C4CE-088F-70C3C6D7372C} corresponds to the following line in the discovery script:
  
  .AddProperty "{02392F7E-2262-C4CE-088F-70C3C6D7372C}", oRSClass.ServiceClusterName
  
  Is this somehow a bug in the MP which I should file on the OpsMgr Connect site, or is there something else wrong?
  
  
  Thanks,
  Mark

  Tuesday, December 21, 2010 6:00 PM