December 5, 2016 at 2:27 pm
Hi,
Background:
Windows Server 2016 Core
SQL Server 2016 Enterprise (obviously 64-bit)
Windows Failover Cluster
SQL Failover Cluster
I am attempting to connect to SQL Server Configuration Manager via my local Computer Management connecting to the database server. I expand Services and Applications and click on SQL Server Configuration Manager. However, this is the error message I see:
Connection failed.
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]
I have tried this in the command prompt:
mofcomp "%programfiles(x86)%\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof"
Which then says:
MOF file has been successfully parsed
Storing data in the repository...
Done!
Then I restart WMI service, close Computer Management, and reopen it. And I get the same error.
Does anyone know how to resolve this?
Thank you!
December 6, 2016 at 12:13 am
This was removed by the editor as SPAM
December 9, 2016 at 5:11 am
December 9, 2016 at 6:45 am
I did that already which was stated in my original post.
This is all of the things that I've done thus far:
http://dba.stackexchange.com/questions/157487/sql-server-2016-configuration-manager-wmi-problem
June 14, 2017 at 5:35 am
dajonx - Friday, December 9, 2016 6:45 AMI did that already which was stated in my original post. This is all of the things that I've done thus far:http://dba.stackexchange.com/questions/157487/sql-server-2016-configuration-manager-wmi-problem
Im in the exacly same boat with two of my 2016 Core servers.
Is this even supported by microsoft? I have googled alot and not found any solution yet.
Done all your posts and more.
My post:
https://www.sqlservercentral.com/Forums/Topic1880568.aspx?Update=1
June 14, 2017 at 6:53 am
Do you have SQL Server 2016 installed on your local machine? I think that is what helped me resolve the issue.
So make sure you have a normal SQL Server 2016 instance installed on your local machine and then open up Computer Management and click on Services, etc. Depending on how many SQL instances you have on your local machine, there could be several SQL Server Configuration Managers on your Computer Management so you will have to go through them.
Let me know how that goes for you!
June 26, 2017 at 4:47 am
dajonx - Wednesday, June 14, 2017 6:53 AMDo you have SQL Server 2016 installed on your local machine? I think that is what helped me resolve the issue.So make sure you have a normal SQL Server 2016 instance installed on your local machine and then open up Computer Management and click on Services, etc. Depending on how many SQL instances you have on your local machine, there could be several SQL Server Configuration Managers on your Computer Management so you will have to go through them.
Let me know how that goes for you!
Yes i have the management Studio 2014+2016 installed and trying to remote access SQL Configuration Manager via a ordinary member server.
Orginal post
Thanks
HA4g3n
Sweden
September 20, 2017 at 5:54 am
I am also facing same issue.
2016 SQL Management Studio and SQL server configuration manager installed in my workstation along side with sql2012 tools. I am trying to connect a remote SQL2016 server from my workstation SQL server Configuration manager.
Error:
From my workstation SQL server Configuration manager
1. I can not connect to remote SQL2016 SQL server Configuration manager
2. I can not connect to another remote SQL2008 SQL server Configuration manager
3. I can connect to another remote SQL2012 SQL server Configuration manager
I have Administrator right in all the three servers. I tried all available solution found online like mofcomp .
September 20, 2017 at 6:22 am
Please make sure that you have SQL 2016 developer edition or something similar installed on your local machine. Then try to access SQL Server Configuration Manager using Computer Management (make sure you connect to the remote server). Then expand Services and Applications and you should see SQL Server Configuration Manager (you may have several like me). Expand each one until one of them works. If that doesn't work, then try the mofcomp command and try again.
April 16, 2018 at 7:44 am
Curious to know if this solution worked for OP. I am having the same problem and I didn't see any resolution on this thread. My configuration is:
Windows Server Core
SQL Server 2017 Enterprise
Trying to manage the server remotely or from a command prompt, but I am getting WMI error 0x8004100E. MOF file solution did not fix my error message.
Ryan
April 16, 2018 at 8:06 am
Yes, the solution works for me. To close the loop on this:
Prior to installing SQL Server Developer 2017 on my computer, I was running computer management for my remote SQL server using the following command:
%windir%\system32\compmgmt.msc /computer:\\{my sql server name here}
And I was receiving the 0x8004100E error when accessing the Services and Applications > SQL Server Configuration Manager node.
I installed SQL Server Developer 2017 on my local computer as suggested (I only installed the database engine option), and reran computer management:
Now an additional SQL Server Configuration Manager node exists under Services and Applications. One node still returns the error message, but the other node is working.
Thanks and sorry to dredge up an old thread, but hopefully this answers questions for those in the future.
Ryan
April 16, 2018 at 8:09 am
ryan.mcatee - Monday, April 16, 2018 7:44 AMCurious to know if this solution worked for OP. I am having the same problem and I didn't see any resolution on this thread. My configuration is:Windows Server Core
SQL Server 2017 EnterpriseTrying to manage the server remotely or from a command prompt, but I am getting WMI error 0x8004100E. MOF file solution did not fix my error message.
Ryan
Please post the error you got when running mofcomp? What is the complete error message when trying to connect using Configuration Manager ?
Did you also run mofcomp using Run As Administrator? Run as administrator is not the same as being in the administrators group.
Sue
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply