Discovery Issue with SQL Databasis
Hi Everyone, We've got multiple SQL2008R1/2 boxes, each with multiple Instances and Databasis. I'm experiencing an issue with one of these boxes as follows: The SQL box have 8 instances and SCOM2007R2 did discover them, but 3 of the Instances, SCOM can't Monitor them. So if you expand the SQL Management Pack 6.1.314.36, under Monitoring>Server Roles>Database Engines then one can see that the Instances in question does not have any check marks next to them where as the rest of the Instances do have check marks. All DBs are replicated to a another SQL box, and on that box, the DBs are discovered and monitored. <<Everyone says that it should have something to do with Permissions>> I'm using one account for the three Profiles: SQL Default Action, Discovery and Monitoring. This domain account used, is a local Admin on the SQL Box and SQLAdmin on all the Instances and their DBs. When looking at the SQL Authentication Logs, I don't see any failed login attempts. We use one specific domain account for all SQL Servers and their Instances and DBs with full access. And for the rest of the other servers on the network, we use a specific domain Account which have local admin rights. So with this in mind, how should the Action account and Profiles be configured for the SQL realm ? When I log on the SCOM Server with the SQL Account used on the SQL boxes and open up SQL Management Studio, I can succesfully expand the Instances in question and their DBs and return rows. Please advise and many thanks.
January 24th, 2011 2:54am

Hi, so according to what you are saying the same databases with same rights on another box are being discovered and monitored. Also other instances with similar rights on the same box are being found. It did sound like permissions at first like you said, so i will skip that part. But if that is not the case, perhaps it helps to flush the cache and let it re-run a complete discovery etc etc. From what you say about the health state view (database engines view) i understand that you do not see checkboxes there, but i assume you do not even see "unmonitored" there either, right? You can stop the healthservice (System Center Management) and delete the contents of the folder C:\Program Files\System Center Operations Manager 2007\Health Service State\*.* and start the healthservice again. This is a bit more than flushing the cache as it also forces the box to download the management packs again etc etc. SO give it 5 minutes to walk through that and another 10 minutes to walk through discovery. I hope it will show you the remaining instances after that (at first unmonitored and later as monitored). Just simply re-starting the agent without throwing anything away will force a re-run of most discoveries within a number of minutes. Let us know what happened after that. Bob Cornelissen - BICTT (My BICTT Blog)
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 5:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics