On an internal SQL Server 2016 instance that we run on a Windows 10 host/OSE, we had SQL Server Management Studio 17.1 installed, and it recently informed us that a new version (17.2) was available. Someone performed that upgrade (I plead the fifth!)– perhaps uninstalling 17.1, and doing the full install of 17.2 SSMS. A few days later (while logging traffic through the network generated by using “runas” to authenticate SSMS to another domain) I found that the local copy of SQL Server Configuration Manager (under Start > Microsoft SQL Server 2016 > Configuration Tools) had disappeared, and we instead had SQL Server 2017 RC1 Configuration Manager (Under Start > Microsoft SQL Server 2017 RC1).

And that would have been fine– but launching it generated an error:

“Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Invalid namespace [0x8004100e]”

Per a whole bunch of older articles I found on DuckDuckGo, such as https://support.microsoft.com/en-us/help/956013/error-message-when-you-open-sql-server-configuration-manager-in-sql-se, I ran

mofcomp “C:\Program Files (x86)\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof”
mofcomp “C:\Program Files (x86)\Microsoft SQL Server\140\Shared\sqlmgmproviderxpsp2up.mof”

This made it so the tool was able to launch, and we could see all of the local SQL services under “SQL Server Services”.

However, “SQL Server Network Configuration” was missing! The “SQL Server Network Configuration (32bit)” section was there, but blank as usual. Searching the web wasn’t turning up much, so I started poking around on the local machine to find the old tool.

Looking on a machine that had 2016 but not the problem, I could see that the command in the Shortcut on the Start Menu for SQL Server Configuration Manager is actually a call to open a Microsoft Management Console (MMC):

C:\Windows\SysWOW64\mmc.exe /32 C:\Windows\SysWOW64\SQLServerManager13.msc

I copied the “SQL Server 2016 Configuration Manager” shortcut file in the folder “C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2016\Configuration Tools” from the donor machine to the one I was having the problem with.

Problem solved. If you run into this, hope it works for you too!

Leave a Reply

Your email address will not be published. Required fields are marked *