Trouble with setup due to SQL not being detected?
Published Feb 15 2019 04:17 AM 270 Views
First published on TECHNET on Oct 26, 2010
If you have run into issues during setup where you know that you have a supported version of SQL running on your machine but setup in unable to detect it, you may have hit a SQL WMI provider issue. In OpsMgr 2007 R2, this shows up as the SQL Server requirement in the Prerequisite Checker failing.

Setup calls WMI in order to check SQL version to determine if the SQL version meets the prerequisites. Once you have verified that you do in fact have SQL installed on the machine and that it is indeed a supported version of SQL, check if the WMI provider is the the issue by trying to connect to SQL using SQL Server Configuration Manager. You should receive an error that reads:

" Cannot connect to WMI provider. You do not have permission or the server is unreachable. Not that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class. "

The solution for this issue is to recompile your MOF file, which can be done using the steps detailed in this blog:

Happy deployment!

Version history
Last update:
‎Mar 11 2019 08:35 AM
Updated by: