Installing SQL Server Dev Config Manager (Snap in)

  • Thread starter Thread starter WWGD
  • Start date Start date
  • Tags Tags
    Server Sql
Join the discussion
Ask a follow-up here, or get your own question answered by working scientists, mathematicians and engineers — people, not an autocomplete.
Real named experts · corrections over time · the nuance an AI answer skips
1 reply · 2K views
Messages
7,819
Reaction score
13,151
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: 696
  • upload_2019-3-14_13-55-16.png
    upload_2019-3-14_13-55-16.png
    56.1 KB · Views: 608
Last edited:
Physics 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.