Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
SCOM 2012 Discovery Problem: The pool managing the instance is not available or the location monitoring object cannot be found

Answered SCOM 2012 Discovery Problem: The pool managing the instance is not available or the location monitoring object cannot be found

  • Wednesday, April 11, 2012 2:02 AM
     
     
    Sign In to Vote
    0

    Hi,

    I have installed SCOM 2012 on a test lab. Everything went smooth but when I tried discovery, the error "The pool managing the instance is not available or the location monitoring object cannot be found.

    Here is my Environment

    Server1 - Windows Server 2008 R2 SP1 - Active Directory

    Server2- Windows Server 2008 R2 SP1 - SQL Server 2008 SP2 (10.0.4000.0)

    Server3 - WIndows Server 2008 R2 SP1 - SCOM 2012

    SQL Broker is working. is_broker_enabled = 1 using the Query SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager'

    I can ping the machine to be discovered. It is part of active directory, it can be resolved, firewall is off.

    I am also using a domain administrator during the discovery.

    Any ideas how to troubleshoot it?

    Regards!

     

All Replies

  • Wednesday, April 11, 2012 5:52 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi

    Check he health of your management servers - in the monitoring view, there is an Operations Manager folder and in there some management server health state views \ dashboards. Are they all healthy?

    Also, take a look at the OperationsManager event log in eventvwr.exe for any errors on server 3.

    It doesn't sound like a permissions problem - you must be a scom admin to see the admin tab to push agents and it sounds like the discovery is not completing.

    Cheers

    Graham

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

     
  • Wednesday, April 11, 2012 6:42 AM
     
     
    Sign In to Vote
    0

    I have tried the entire thing again but this time using SQL Server 2008 R2.

    Everything is fine now.

    Server2- Windows Server 2008 R2 SP1 - SQL Server 2008 SP2 (10.0.4000.0)

    Can we conclude that the error im having is that SQL Server 2008 SP2 is not supported?

    Regards

     
  • Wednesday, April 11, 2012 6:43 AM
     
     
    Sign In to Vote
    0

    The health of the management server is Off as if it is not being monitored.

     
  • Wednesday, April 11, 2012 6:49 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Certainly SP2 is not listed on supported configurations:

    http://technet.microsoft.com/en-us/library/hh205990.aspx#BKMK_RBF_OperationsDatabase

    Is the management server still unhealthy when using SQL 2008 R2 (with \ without SP1)?

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


     
  • Wednesday, April 11, 2012 9:19 AM
     
     
    Sign In to Vote
    0

    The management server is now ok using SQL 2008 R2.

    This one is working now.

    Thanks!

     
  • Friday, April 20, 2012 1:41 PM
     
     
    Sign In to Vote
    0

    I'm currently encountering the same issue with the RTM release of SCOM... and I'm definitely using SQL 2008 R2 SP1. There doesn't seem to be any other info on Technet or anywhere else. 

    Can you offer any other insight on to why this could be happening? 

     
  • Friday, April 20, 2012 1:45 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hi

    Can you confirm the architecture again as this is now production, especially how many management servers you have and are the agents you are trying to deploy in the same domain as the management Servers?

    E.g.

    Server 1 = SQL with all SCOM databases

    Server 2 = Management Server 1

    Server 3 = Management Server 2

    Cheers

    Graham

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

     
  • Thursday, May 03, 2012 12:15 PM
     
     
    Sign In to Vote
    0

    Hi

    I am facing the same error.

    I installed SCOM 2012 RTM.

    Server1= SQL 2008 R2 Sp1 CU6 with all SCOM databases

    Server2=SCOM2012

    I tried few things, setting up SPN for sdk account, reinstalling scom console. But no luck.

    Suggestions please.

     
  • Friday, May 11, 2012 6:50 PM
     
     
    Sign In to Vote
    0

    I am running into the same issue. After getting past a SQL bug, and a initial installation isuse, I have things installed, but cannot discover objects.

    SCOM 2012 RTM + CU1
    SQL 2008 R2 Sp1 CU6 (minus Reporting Services)

    Microsoft.EnterpriseManagement.Common.LocationObjectNotFoundException: The pool managing the instance is not available or the location monitoring object cannot be found.
       at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
       at Microsoft.EnterpriseManagement.Common.Internal.AdministrationServiceProxy.LaunchDiscovery(Guid batchId, IList`1 jobDefinitions)
       at Microsoft.EnterpriseManagement.Administration.ManagementServer.BeginExecuteWindowsDiscovery(IList`1 discoveryConfigurations, AsyncCallback callback, Object state)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Administration.DiscoveryProgress.<>c__DisplayClass7.<SubmitTask>b__3(Object , ConsoleJobEventArgs )
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

    Also the SQL Broker is enabled
    • Edited by LTParisTW Friday, May 11, 2012 7:44 PM
    •  
     
  • Monday, May 14, 2012 4:32 AM
     
     
    Sign In to Vote
    0

    Same problem 2008 R2 as well.


     
  • Thursday, May 17, 2012 5:59 PM
     
     
    Sign In to Vote
    0
    I am a little dismayed there is no real discussion on this issue yet.
     
  • Saturday, June 09, 2012 10:53 PM
     
     
    Sign In to Vote
    0
    Same issue here, 2008 R2 SQL 2008 R2 SP1, Broker enabled etc.
     
  • Monday, June 11, 2012 10:46 PM
     
     
    Sign In to Vote
    0

    The problem is resolved for me when I start the SQL server browser service. It was set to start "Manual"

    I am now able to discover all machines on the network with no error. go figure.