There appears to be an issue when trying to discover certain SQL 2008 instances with SCOM. Which is related to MOF data not being registered in the WMI repository correctly when SQL is installed.
The error that you will see in your Operations Manager event log is:
DiscoverSQL2008DBEngineDiscovery.vbs : The Query ‘select * from SqlService where SQLServiceType =’1” did not return any valid instances. Please check to see if this is a valid WMI Query.. Invalid class
I’ve had success with the below solution:
From an elevated command prompt, browse to the folder “C:\Program Files (x86)\Microsoft SQL Server\100\Shared”
This article is about an issue experienced with SCOM SMS notifications after upgrading from SCOM 2007 R2 to SCOM 2012. If you are looking for how to setup SMS notifications in SCOM in general I’d recommend this great article by Jeremy Pavleck (http://www.pavleck.net/2009/04/configuring-sms-in-opsmgr/)
We use a GSM modem in order to send alerts via SMS to our engineers. After upgrading to SCOM 2012 however this method stopped working and we started getting the following alert in the console.
Notification subsystem failed to locate (discover) devices/servers to use to send notification over ‘SMS’ protocol or no devices/servers were provided in configuration. All notifications for ‘SMS’ protocol will not be sent. Rule id: Subscriptionaad09d28_a5b8_4b24_ad06_7b0145a34e79
This was quite strange as testing with the modem software, it was possible to successfully send a test SMS.
As it turns out the issues lies with the Notification Resource Pool, in order to get SCOM to successfully send SMSs again I had to switch the resource pool to manual membership and remove all management servers from the pool with the exception of the one with the modem attached. Now everything is working again.
During our SCOM 2012 upgrade I came across some 2007 agents would not upgrade to 2012 due to being unable to complete the uninstall portion of the agent installer.
Errors we experienced included corrupt MSIEXEC packages and a rollback of the 2012 agent upgrade with the message “unable to install performance counters.”
After attempting manually uninstalling from Add / Remove programs as well as the SCOM 2007 removal tool with no success we came across a tool called MSIZAP. (Thanks to Jonathan Almquist for his great blog post pointing us in the right direction)
The following process will allow you to remove the SCOM agent from your servers which will in turn allow you to install your new 2012 agent: As always backup your registry before attempting any process that makes changes to it.
Download MSIZAP and copy to a location on the affected computer.
Find the product code, which is a GUID that is required for the MSIZAP product code switch. This can be found by opening the registry and navigating to:HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
With the Uninstall key highlighted, click on Edit > Find, and look for the string System Center Operations Manager. Open the UninstallString string value, and copy the GUID. Include the squiggly brackets.
3. Open an elevated command prompt and run the program as follows:
4. Delete the SCOM program files, usually located under “%ProgramFiles%\System Center Operations Manager 2007”. Some files may be locked those can be ignored.
5. Open the registry, search for the Management Group name
6. Delete the Microsoft Operations Manager key that the management group name is part of
7.Open the registry and navigate to:
HKLM\System\CurrentControlSet\Services
Delete the following registry entries:
healthservice
opsmgr*
MOMConnector
System Center Management APM (2012 only)
8. Reboot the server
You will now be able to install your agent manually or with your console.
