Sql server configuration manager ошибка

In some cases where you might try to launch SQL Server Configuration Manager, you might get the error message: 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]

Is SQL Server Configuration Manager Really Needed?

Easy answer: of course it is!

Even though you can still control SQL Server services via Windows Services (services.msc), in order to have full control, you still need SQL Server Configuration Manager.

For example, if you want to set up SQL Server in order to use SSL certificate you need SQL Server Configuration Manager.

Moreover, if you want to change the network settings for your SQL Server services, again, you will need SQL Server Configuration Manager.

There are more examples that can justify the usefulness of SQL Server Configuration Manager but, I’m pretty sure you got the picture 🙂

Learn more tips like this! Enroll to our Online Course!

Check our online course titled “Essential SQL Server Administration Tips” (special limited-time discount included in link).

Learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Enroll from $12.99

Why I Got this Error Message?

If you performed several installations and uninstallations of SQL Server components on the machine, then under certain circumstances thi might cause the abovementioned issue with SQL Server Configuration Manager.

How to Get SQL Server Configuration to Work Again

As per Microsoft’s official support documentation, you can easily fix this issue.

So, in order to fix the issue, you can open an elevated command prompt (Run as Administrator) and execute the below command, after of course you replace “number” with the version of SQL Server in terms of number.

mofcomp "%programfiles(x86)%Microsoft SQL ServernumberSharedsqlmgmproviderxpsp2up.mof"

In order to find the right version number, please check the below table:

So, if for example, you want to fix the SQL Server 2016 Configuration Manager, you would run the below command in an elevated command prompt (Run as Administrator):

mofcomp "%programfiles(x86)%Microsoft SQL Server130Sharedsqlmgmproviderxpsp2up.mof"

An Alternative Way to Launch SQL Server Configuration Manager

Last but not least, there is an alternative approach to start SQL Server Configuration Manager. Again, from the command line, you can run the corresponding command for each SQL Server version as provided in the below table:

Featured Online Courses:

• SQL Server 2022: What’s New – New and Enhanced Features [New]
• Data Management for Beginners – Main Principles
• Introduction to Azure Database for MySQL
• Working with Python on Windows and SQL Server Databases
• Boost SQL Server Database Performance with In-Memory OLTP
• Introduction to Azure SQL Database for Beginners
• Essential SQL Server Administration Tips
• SQL Server Fundamentals – SQL Database for Beginners
• Essential SQL Server Development Tips for SQL Developers
• Introduction to Computer Programming for Beginners
• .NET Programming for Beginners – Windows Forms with C#
• SQL Server 2019: What’s New – New and Enhanced Features
• Entity Framework: Getting Started – Complete Beginners Guide
• A Guide on How to Start and Monetize a Successful Blog
• Data Management for Beginners – Main Principles

Read Also

Feel free to check our other relevant articles on SQL Server troubleshooting:

• Error converting data type varchar to numeric
• The Database Engine system data directory in the registry is not valid
• Error converting data type varchar to float
• An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpoint (9642) – How to Resolve
• There is not enough space on the disk. (mscorlib)
• A network-related or instance-specific error occurred while establishing a connection to SQL Server
• SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)
• ORDER BY items must appear in the select list if SELECT DISTINCT is specified
• There is no SQL Server Failover Cluster Available to Join
• There is insufficient system memory in resource pool ‘internal’ to run this query.
• The SELECT permission was denied on the object ‘extended_properties’, database ‘mssqlsystemresource’, schema ‘sys’.
• The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value
• SQL Server replication requires the actual server name to make a connection to the server – How to Resolve it
• Issue Adding Node to a SQL Server Failover Cluster – Greyed Out Service Account – How to Resolve
• initerrlog: could not open error log file. Operating system error=3 … – How to Resolve It
• Resolve SQL Server CTE Error – Incorrect syntax near ‘)’.
• SQL Server is Terminating Because of Fatal Exception 80000003 – How to Troubleshoot
• An existing History Table cannot be specified with LEDGER=ON – How to Resolve
• … all SQL Server troubleshooting articles

Featured Database Productivity Tools

Snippets Generator: Create and modify T-SQL snippets for use in SQL Management Studio, fast, easy and efficiently.

Learn more

Dynamic SQL Generator: Convert static T-SQL code to dynamic and vice versa, easily and fast.

Learn more

Subscribe to our newsletter and stay up to date!

Check out our latest software releases!

Check our eBooks!

Rate this article: (3 votes, average: 5.00 out of 5)

Loading…

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub

Views: 14,483

Hi,

My Os is Windows 7 Enterprise.

I have Sql Server 2008 Developer Edt. with sp1

and Sql Server 2005 express (which comes with Visual Studio)

When I try to open Configuration Manager it fails:

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 server with SQL Server Configuration Manager.

Invalid class [0x80041010]

I’ve tried everything I could find on the net. But none of them worked for me.

Later, I realised that the file called «sqlwep-uni.mof» under «c:Program FilesMicrosoft SQL ServerMSSQL10.INSTANCENAMEMSSQLBinn» has failed with mofcomp command.

Hi,

My Os is Windows 7 Enterprise.

I have Sql Server 2008 Developer Edt. with sp1

and Sql Server 2005 express (which comes with Visual Studio)

When I try to open Configuration Manager it fails:

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 server with SQL Server Configuration Manager.

Invalid class [0x80041010]

I’ve tried everything I could find on the net. But none of them worked for me.

Later, I realised that the file called «sqlwep-uni.mof» under «c:Program FilesMicrosoft SQL ServerMSSQL10.INSTANCENAMEMSSQLBinn» has failed with mofcomp command.

Posted by blakhani on September 4, 2014

This entry was posted on September 4, 2014 at 3:30 AM and is filed under Error, Troubleshooting.
Tagged: Cannot connect to WMI provider, Invalid class [0x80041010], Invalid namespace [0x8004100e], sql server configuration manager. You can follow any responses to this entry through the RSS 2.0 feed.

You can leave a response, or trackback from your own site.

  cd C:Program Files (x86)Microsoft SQL Server110Shared
  cd C:Program Files (x86)Microsoft SQL Server140Shared
  mofcomp sqlmgmproviderxpsp2up.mof

SQL 2008: C:Program Files (x86)Microsoft SQL Server100Shared
SQL 2012: C:Program Files (x86)Microsoft SQL Server110Shared
SQL 2014: C:Program Files (x86)Microsoft SQL Server120Shared
SQL 2017: C:Program Files (x86)Microsoft SQL Server140Shared 
SQL 2019: C:Program Files (x86)Microsoft SQL Server150Shared

Насколько полезной была статья?

Что еще посмотреть по SQL Server