How does database WMI 0 × 80041010 be solved?

Event cause:

Because the second data center charging system is required, the database is essential. however, I have installed vs2010. When I connect to the database, I am reminded that sql2010 is not supported, and 2005 and later versions are supported. (However, later, the meeting will know that it is not unusable, some settings are required, but I have uninstalled SQL2000 and installed sql2008), because I was worried that SQL2000 would not be deleted. so I made some preparations before the deletion and checked the relevant information online. the cause of this problem is related to the deletion of SQL2000. Some files cannot be deleted when SQL2000 is deleted. the folder address is "C: \ Program Files \ Microsoft SQL Server", and I accidentally deleted the file. later, when sql2008 was installed again, an error will occur immediately after the end, and it cannot be installed frequently. I guess it was because I deleted the file by mistake. after that, let the glory contest help me copy the files in the folder. then install it again. successful!

However, when I open the configuration management option after installation, an error is displayed as a slice.

How can we solve the above problems?

Knowledge Point: WMI (Windows Management Instrumentation, Windows Management specifications) is a core windows management technology. You can use WMI to manage local and remote computers. This knowledge will only be used for further learning.

I started to look for it from the Internet, but before I looked for it, I came up with an idea. I used to find related solutions through Baidu, during a winter vacation, I almost studied English for English materials. This time I tried to find related solutions on a foreign website. just make a try.

Found related resources

First:

SQL Server-WMI error 0x80041010-invalid class

Recently I started experiencing WMI Repository resume uption that results in inability to open SQL Server Configuration Manager with the following 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 class [0x80041010]

At this point if I browse WMI Repository under Root \ Microsoft \ sqlserver \ computermanagement11 I see no SQL Server-specific classes. only system classes exist. to resolve this issue SQL Server WMI provider needs to be reinstalled.

Step 1-install classes

Navigate to c: \ Program Files (x86) \ Microsoft SQL Server \ <SQL Server version, for example "110" for SQL Server 11> \ shared if you have x64 installation of SQL Server. on x86 machine the path is c: \ Program Files \ Microsoft SQL Server \ <SQL Server version, for example "110" for SQL Server 11> \ shared. make sure that file sqlmgmproviderxpsp2up. MOF exists. if it doesn't then either you're in the wrong location or your installation is already upted and only SQL Server Setup can fix the problem. however if the file does exist, then resolution is as simple as running command:

Mofcomp sqlmgmproviderxpsp2up. mof

WMI compiler will modify y you that repository was successfully updated

Step 2-install localization Information

After the classes are deployed localization information needs to be installed as well. from the path in the previous step navigate to the sub-folder that reflects the locale of SQL Server installation. for example 1033 (for English-US ). full path is now c: \ Program Files (x86) \ Microsoft SQL Server \ <SQL Server version, for example "110"> \ shared \ <locale ID, for example "1033" for English>. when at this path run the following command:

Mofcomp sqlmgmprovider. MFL

WMI resopitory shoshould have been updated successfully again.

Now you're all set. the problem shocould be resolve and SQL Server Configuration Manager shocould be functional again. if it still isn't the I wocould encourage you to describe your problem at SQL Server manageability Forum-http://social.msdn.microsoft.com/Forums/en-US/sqlkjmanageability/threads

Source Document

The above English mainly means that he has encountered the same problem as me. the cause is a file problem. The file name is sqlmgmproviderxpsp2up. MOF: Check whether a file exists. If it does not exist, update the file and run the code in the running box.

Mofcomp sqlmgmproviderxpsp2up. mof

After that, WMI will notify you that the update is successful, but the following error occurs when I follow this method.

The first step fails, and the second step does not need to be viewed, so you can find other methods.

After finding other websites to solve the same problem, you can confirm that the problem occurs on the sqlmgmproviderxpsp2up. mof file. But the specific operations are not the same. (The path is added)

Second:

SQL Server Configuration Manager-cannot connect to WMI provider-invalid class [0x80041010]

When I am trying to connect to My SQL Server 2008 box using SQL Server Configuration Manager today, the following error dialog pops up...

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 class [0x80041010]

I have never seen this before !... While the following line saves me.

> Open an elevated command prompt, and type the following...

Mofcomp.exe "C: \ Program Files (x86) \ Microsoft SQL Server \ 100 \ shared \ sqlmgmproviderxpsp2up. MOF"

The solution is similar to the first one, but more specific. then I will execute it in his way. however, it still fails (in fact, it can be successful just a little bit now ). as follows:

I didn't solve this problem last night because of time problems. I felt very uncomfortable. So I thought I would like to bring my computer back to my dormitory, re-install sql2008. but the tragedy is that when the installation is completed by, the same problem still exists in the configuration management ...... so I went to bed. (~ Region ﹃~)~ Zz

In the evening, it seems that the database is being installed.

We got up early today and thought we should solve this problem at the data center. I still haven't finished it after half an hour. finally, let us have a look at it and ask me if it is a path problem. in a word, the sky is broken. in fact, there is no problem with the path. The key is that the (x86) problem is true here. After Entering the path of my own file, the update is successful!

As follows:

Reflection and summary

My error causes:

1 (x86) is not careful enough.

The original author's command is: mofcomp.exe "C: \ Program Files (x86) \ Microsoft SQL Server \ 100 \ shared \ sqlmgmproviderxpsp2up. MOF"

My command is: mofcomp.exe "C: \ Program Files \ Microsoft SQL Server \ 100 \ shared \ sqlmgmproviderxpsp2up. MOF"

For 32-bit (x86) and 64-bit (x64) explanations in windows, see the link.

2. Do not delete files that you are not clear about.

Gains:

This is the first time I tried to find relevant solutions in English. Later, Baidu found that most of the answers were translated from abroad and I realized the importance of English!