locked
SQL Server reporting service doesn't get undiscovered RRS feed

  • Question

  • Hi All,

    We have a SCOM 2007 R2 infra with SQL Server Management Pack v6.3.173.1. Yesterday I've uninstalled 2 SQL Server Reporting Services instances, but SCOM still thinks they are present and healthy. Going through the service (SQL Server Configuration Manager & Services.msc) the services are nowhere to be found? The discovery runs every 4 hours, so should have detected that the instances were removed.

    The workaround I used before was to uninstall the agent (and thus removing everything from SCOM). This made sure it got removed from the console and discovered inventory, but shouldn't be necessary.

    Does anyone else ever encountered something like this? And with did you do to resolve it (and isn't as drastic as the workaround I describe above)?

    Kinds regards,

    Mark

    Tuesday, September 11, 2012 7:21 AM

Answers

  • Mark,

    yes the 'issue' is related to the database. once an agent is discovered with something it stays that way. I had seen posts when folks would uninstall agent to get it to un-discover something but that does not always work b/c the agent and all its discovery data would not be out of the db before they re-install the agent.

    following Jonathan's blog http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx

    Making sure the registry entries are gone for the application that is being discovered, I'm not sure that will help much, as there needs to be an override created for the discovery rule for the specific system so that it is FALSE, then running the cmdlet Remove-DisabledMonitoringObject should remove this application. Remove-DisabledMonitoringObject will only remove inventory that has already been discovered, for objects that have an override for Enable = FALSE explicitly for the discovery rule. 

    I had mentioned bouncing the RMS Services to make sure there was not something stuck in the RMS Queue that was not updating the console. Oh yeah did you ever clearcache on the console to make sure it was not the console too? 

    Hope this helps.


    Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
    Please remember to click “Mark as Answer” on the post that helps you!
    my new blog om2012.wordpress.com



    • Edited by ScottMoss Wednesday, October 17, 2012 7:36 PM
    • Proposed as answer by ScottMoss Wednesday, October 31, 2012 6:18 PM
    • Marked as answer by ScottMoss Sunday, November 25, 2012 1:35 AM
    Wednesday, October 17, 2012 7:29 PM

All replies

  • Hi Mark

    Override the SQL Reporting Services discovery for those 2 servers and then remove-disabledmonitoringobject:

    http://technet.microsoft.com/en-us/library/gg132269.aspx

    http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx

    That should do the trick.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Tuesday, September 11, 2012 7:49 AM
  • Hi Graham,

    I've overwritten the discovery (Discover SQL Server 2008 Reporting Services (Windows Server)) for the specific objects an ran remove-disabledmonitoringobject twice, but this doesn't change the story. Still both instances are there in the operations console.

    Kind regards,

    Mark

    Tuesday, September 11, 2012 9:14 AM
  • Ok, time has passed. Unfortunately the instances are still present in the OpsMgr console (and healthy). Has anyone else encountered this?
    Friday, September 14, 2012 11:38 AM
  • Latest update, this doesn't only seem to happen for the reporting services instances, but also for the DB Engines.

    Friday, September 21, 2012 11:43 AM
  • Have you tried restarting the healthservice on these SSRS boxes? If not try the following:

    Stop the "System Center Healthservice" - rename the "Health Service State" folder (usually located under C:\Program Files\System Center Operations Manager\Agent) and restart the "System Center Healthservice"

    This should update the SSRS status in SCOM.


    MA

    Thursday, October 11, 2012 3:59 PM
  • Hi Murad,

    Last friday I've stopped the healthservice and removed the "Health Service State" folder from the affected systems. Unfortunately the removal of SSRS still isn't detected by SCOM.

    Regards,

    Mark

    Tuesday, October 16, 2012 9:24 AM
  • Have you tried bouncing the opsmgr services on the rms or ms the server reports too and clean up the health folder too?

    Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
    Please remember to click “Mark as Answer” on the post that helps you!
    my new blog om2012.wordpress.com

    Wednesday, October 17, 2012 2:34 AM
  • i think you probably need to figure out what the discovery triggers. e.g. it might be some regkey that's still present despite the reporting services has been removed.

    it might also be something similar to http://jama00.wordpress.com/2011/01/26/scoms-un-discovery-what-doesnt-work-here-and-how-to-correct-it (i've never seen this with the SQL mp)


    Rob Korving
    http://jama00.wordpress.com/


    • Edited by rob1974 Wednesday, October 17, 2012 5:38 AM
    Wednesday, October 17, 2012 5:34 AM
  • Hi All,

    The funny thing about this issue is that when I remove the SCOM agent and reinstall it again. The SSRS isn't detected anymore, so it seems it is stuck on the management group side, not on the agent. Removing the agent makes sure that is removed from all central places.

    Stopping/restarting the services on the RMS doesn't seem a plan,this causes a number of agents to lose connection. Not really something I would like to do!

    Regards,
    Mark

    Wednesday, October 17, 2012 10:30 AM
  • Mark,

    yes the 'issue' is related to the database. once an agent is discovered with something it stays that way. I had seen posts when folks would uninstall agent to get it to un-discover something but that does not always work b/c the agent and all its discovery data would not be out of the db before they re-install the agent.

    following Jonathan's blog http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx

    Making sure the registry entries are gone for the application that is being discovered, I'm not sure that will help much, as there needs to be an override created for the discovery rule for the specific system so that it is FALSE, then running the cmdlet Remove-DisabledMonitoringObject should remove this application. Remove-DisabledMonitoringObject will only remove inventory that has already been discovered, for objects that have an override for Enable = FALSE explicitly for the discovery rule. 

    I had mentioned bouncing the RMS Services to make sure there was not something stuck in the RMS Queue that was not updating the console. Oh yeah did you ever clearcache on the console to make sure it was not the console too? 

    Hope this helps.


    Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
    Please remember to click “Mark as Answer” on the post that helps you!
    my new blog om2012.wordpress.com



    • Edited by ScottMoss Wednesday, October 17, 2012 7:36 PM
    • Proposed as answer by ScottMoss Wednesday, October 31, 2012 6:18 PM
    • Marked as answer by ScottMoss Sunday, November 25, 2012 1:35 AM
    Wednesday, October 17, 2012 7:29 PM