SCOM DiscoverSQL2005DBEngineDiscovery.vbs : Unable to open WMI Namespace

The other day at work, I was checking some eventlogs inside of the Operations Manager log of a particular server because of an unrelated issue we were having.

I found out, that every four hours the following ‘Error’ Event messages were being logged in the ‘Operations Manager’ log:

Event ID 4001

DiscoverSQL2005DBEngineDiscovery.vbs : Unable to open WMI Namespace ‘winmgmts:\\SERVER.DOMAIN \root\Microsoft\SqlServer’. Check to see if the WMI service is enabled and running, and ensure this WMI namespace exists..

Event ID 4001

DiscoverSQL2005DBEngineDiscovery.vbs : The Query ‘select * from __NAMESPACE where Name =’ComputerManagement” returned an invalid result set. Please check to see if this is a valid WMI Query.. Object required.

So this doesn’t look good, apart from having these ugly criticals spammed in my log, I dont think it’s healthy from a performance perspective of this particular agent on this server. (AND SQL 2005? Back to the stone age)

Looking at the configuration tab of the ‘object discovery’ inside the ‘Authoring’ pane in the SCOM Console. I found out that the SQL 2005 discovery (or to be more specific: SQL Server 2005 Installation Seed) is looking for the following keys to tell SCOM this is in fact a SQL 2005 Server:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90

SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90

I was completely baffled when finding the above keys on the particular server 😛

Apparently someone installed SQL Server or SQL Server Management Tools (< more likely) and didnt unninstall this in a proper way 😛 ( < VERY LIKELY)

So I checked which servers had this ‘problem’, and I found out it was a bit more than this 1 I was inspecting. (and they werent database servers)

Finding instances discovered by this object discovery

Finding a bit more than 1 😛

So I created a group and filled it with these servers. The next step that I took was making an override for the discovery of the ‘SQL Server 2005 Installation Seed’ and disabled the discovery for my newly created group. And voila! The Operations Manager Event logs on my servers lived long and happily.

System Center Data Access Service won’t start after SCOM 2012 Upgrade

After upgrading the RMS in a SCOM 2007 r2 upgrade scenario to SCOM 2012 there is an issue starting the System Center Data Access Service. It won’t start during the default timeout. (event id 7009)

to fix this, apply the following registery key:

quoted from KB2730040 http://support.microsoft.com/en-us/kb/2730040

To increase the default service time-out, follow these steps:

1.Click Start, click Run, type regedit in the Open box, and then click OK.
2.Locate and then select the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3.Right-click Control, point to New, and then click DWORD.
4.In the New Value box, type ServicesPipeTimeout, and then press Enter.
5.Right-click ServicesPipeTimeout, and then click Modify.
6.Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.

For example, to wait 60 seconds before the service times out, type 60000.
7.On the File menu, click Exit, and then restart the computer.