Permissions required for discovering SQL Server
HI All
We have SQL servers (2008SP2) that are discovered in SCOM 2007 R2 as Windows OS but SQL instance is not discovered
Servers are 2008 R2 SP1. We use local system as default agent action account
We downloaded the latest SQL MP as well. We created run as account that has local admin, SA rights and log on locally rights.
Then associated it with all 3 SQL Run as profiles and distributed to 3 SQL computers
Those SQL computers gets the new config and we see event id 1210 But still no success in discovering SQL Instance
ANything we are missing or how to fix this?~Cheers, Rohit Kochher
June 25th, 2012 3:26pm
Hi,
do you using a latest SQL MP? Old SQL MP has a dependency on a SQL DMO (wich isn't installed by default on a SQL 2008\2008 R2).
http://OpsMgr.ru/
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2012 10:56pm
Yes we are using latest MP
6.3.173.0 version and we have SQL 2008 R2 on 2008 R2 Sp1 OS~Cheers, Rohit Kochher
June 26th, 2012 1:20am
Hi Rohit
I notice that you mention SP2 for SQL 2008 - Is this your issue:
http://nocentdocent.wordpress.com/2012/03/30/including-sql-server-2008-service-pack-2-in-the-database-engine-group/
Cheers
GrahamRegards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2012 3:08am
Hi Graham
I checked with DBA team and we have SQL 2008 R2.
Is this still required?
Also we got latest SQL MP 6.3.173.0~Cheers, Rohit Kochher
June 26th, 2012 10:07am
Hi,
Please also refer to the Security Considerations section of the management pack guide:
System Center Monitoring pack for SQL Server
http://www.microsoft.com/en-us/download/details.aspx?id=10631
Hope this helps.
Thanks. Nicholas Li
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2012 10:25pm
Hi Rohit
Are you getting any run as account errors or is there any error in the operations manager event logs?
Donald D'souza (http://donald-scom.blogspot.com/)
June 27th, 2012 5:13am
HI All
We were getting event 21407 on SQL machine. I deleted the agent on server. Reinstalled it and patched it with CU2
Unfortunately we have CU2 and Cu5 is planned for next week. Not sure if that is the reason for SQL 2008 R2 not being discovered. But its being on other servers.
But even after agent reinstall we again got bunch of 21407. I ran those SQL discovery VB scripts manually and still SQL instance is not being discovered.
How to work on 21407?
~Cheers, Rohit Kochher
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 12:38pm
Update
We follow blog below which fixed event 21407
http://blogs.msdn.com/b/distributedservices/archive/2009/11/06/a-com-server-application-may-stop-working-on-windows-server-2008.aspx
CLeared health cache but still SQL not discovered
no error/warning on those agents
Any ideas?~Cheers, Rohit Kochher
June 28th, 2012 12:27pm
Hi,
Please ensure the agent installed on the server has the same architecture with the Windows Server.
At this time, please also try the following on the management server and see how it works:
1. Clear the HealthService queue:
1) Stop System Center Management service.
2) Go to C:\Program Files\System Center Operations Manager 2007\, and rename the Health Service State folder.
3) Restart System Center Management service.
2. Restart the related services:
System Center Management service
System Center Management Configuration service
System Center Data Access service
Meanwhile, please check the issue referring to the following post:
OpsMgr (SCOM) Discovery stalling Kerberos issue Using SQL 2008
http://blog.binaryfactory.ca/2010/02/opsmgr-scom-discovery-stalling-kerberos-issue-using-sql-2008/
In addition, please check the Event Log again on both the SQL Server and the management server.
Hope this helps.
Thanks. Nicholas Li
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2012 5:56am
HI All
Sorry for late response
Finally we got the resolution. We noticed we were unable to see SQL services listed in SQL configuration manager.
We applied the KB http://support.microsoft.com/kb/941823
basically gave network service read only permissions on SQL server instance
Restarted SCOM agent service on SQL computers
Bang....10 minutes and all databases are getting monitored
Thanks everyone for help!!~Cheers, Rohit Kochher
July 25th, 2012 11:56am