I have a brand new install of SCOM 2012 and I am unable to perform discovery: "The pool managing the instance is not available or the location monitoring object cannot be found." I have tried everything at the following link to no avail: http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/93b8d663-5d4c-438c-b877-75fbf19a2450?prof=required Has anyone else come up with other solutions? SCOM 2012 with SQL Server 2008 R2 SP1 (I originally had 2008 R2 with hopes that SP1 would solve the situation)

If this is brand new with no agents deployed, can you reboot both SQL Server and the Management Servers (in that order). Then, if the problem persists, look at the Operations Manager event log on the Management Servers for errors and warnings. Post them back here. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

No change after reboot: A new client has connected. User name: stamp\omdas Session ID: uuid:8163fea1-90c9-4f6e-a5cd-87109803dd8d;id=2Error occured on database connection: Status: 0x00200001 ODBC Error: 17 ODBC State: 08001 Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Database: Register Connection: ComplianceTest Statement: - Error occured on database connection: Status: 0x00040000 ODBC Error: 67 ODBC State: 01000 Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Database: Register Connection: ComplianceTest Statement: - An exception was thrown while processing LaunchDiscovery for session ID uuid:8163fea1-90c9-4f6e-a5cd-87109803dd8d;id=1. Exception message: The creator of this fault did not specify a Reason. Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.LocationObjectNotFoundException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.LocationObjectNotFoundException: The pool managing the instance is not available or the location monitoring object

Hi This is the clear error Status: 0x00200001 ODBC Error: 17 ODBC State: 08001 Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Database: Register Connection: ComplianceTest Statement: - Chances are the omdas account doesn't have the required rights on the Operations Manager databases. We can double check this by looking at the SQL Server error log. Within SQL on the Operations Manager SQL Server can you check the following permissions on the account against the OperationsManager database: Server role = public Database role = ConfigService role, db_accessadmin, db_datareader, db_datawriter, db_ddladmin, db_securityAdmin, public and sdk_users Cheers Graham Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

thanks for the fast response! The permissions are correct. Added the SCOM_Admins group into the Local Administrators of the DB server group with no change. Finally changed logon for DB services to omdas. I am still getting the same errors.

Can you check the SQL Server error log to see if there are any errors there? Just want to confirm that it is a login error from the SQL side. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Thanks so much for leading me in the right direction I realized that I had modified the password for the service account previously and didn't change it on the DB. this is what happens when you work on something and then come back to it after a few weeks. thanks again!