Installing SQL Server Dev Config Manager (Snap in)

  • Thread starter Thread starter WWGD
  • Start date Start date
  • Tags Tags
    Server Sql
Click For Summary
SUMMARY

The SQL Server 2017 Configuration Manager is not built-in and must be installed as a snap-in. Users may encounter the "Cannot connect to WMI provider" error due to permission issues or server unreachability. A workaround involves using the command line to execute the mofcomp command with the appropriate version number, which for SQL Server 2017 is 140. If issues persist, uninstalling and reinstalling the Configuration Manager is recommended.

PREREQUISITES
  • Familiarity with SQL Server 2017 installation processes
  • Understanding of WMI (Windows Management Instrumentation) errors
  • Basic command line usage in Windows
  • Knowledge of SQL Server instance types (32-bit vs 64-bit)
NEXT STEPS
  • Research the command line usage of mofcomp for SQL Server
  • Learn about troubleshooting WMI provider issues in SQL Server
  • Explore SQL Server Profiler filtering techniques
  • Investigate the differences between 32-bit and 64-bit SQL Server instances
USEFUL FOR

Database administrators, SQL Server developers, and IT professionals involved in SQL Server configuration and troubleshooting.

WWGD
Science Advisor
Homework Helper
Messages
7,796
Reaction score
13,095
Hi All,
It seems SQL Server's Dev 2017 config manager does not come " built in" within , and it is now a snap in. When I try to install it through Control Panel, I get the error message: Cannot connect to WMI provider. You do not have permission or the server is unreachable.
upload_2019-3-14_13-44-59.png


https://support.microsoft.com/en-us...en-sql-server-configuration-manager-in-sql-se

Suggests as a work around to go to the command line and enter:
mofcomp "%programfiles(x86)%\Microsoft SQL Server\number\Shared\sqlmgmproviderxpsp2up.mof" (**)

Where number is in the list given. BUT no numbers are assigned for versions after 2012. In my Microsoft SQL Server folder I have subfolders numbered 80,90, 110, 120, 140.

upload_2019-3-14_13-55-16.png


It would seem I should use 140 as a number in (**) above.
Is this correct?

In the page linked above, it says that the problem comes from having a 32-bit instance and another 64-bit instance, but both my instances are 64-bit.
Thanks.

EDIT: While we're at it, if someone knows how to filter within Profiler, I would appreciate any advice on how to do it.
 

Attachments

  • upload_2019-3-14_13-44-59.png
    upload_2019-3-14_13-44-59.png
    44.8 KB · Views: 682
  • upload_2019-3-14_13-55-16.png
    upload_2019-3-14_13-55-16.png
    56.1 KB · Views: 597
Last edited:
Computer science news on Phys.org
Never mind, thanks, I found a folder containing the needed file --it was 140-- and made the change, needed to compile a n .mof. Still, it did not work out, so I will uninstall and reinstall.
 

Similar threads