Resolved: unable to connect to the WMI provider. You do not have permission or the server cannot access/cannot connect to WMI provider. You do not have permission or ......

I want to use SQL Server to create a database job. I want to use ASP to create a web page. First, you need to install SQL Server. At first, it was very simple. In my Visual Studio 2008 installation package, there was SQL
Server 2005 express edition Installation Software, just install it directly. Which of the following processes is hard ......
First Install SQL Server 2005 (In English version). The installation process is very smooth. Then I want to enter the Server Configuration Manager. After clicking it, the following warning box is displayed:

Search the Internet, find a solution on a foreigner's blog :( http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx)

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.

Invalid class [0x80041010]

The solution is to go to a command prompt and then run mofcomp.

C: \ Program Files \ Microsoft SQL Server \ shared> mofcomp "C: \ Program Files \ Microsoft SQL Server \ shared \ sqlmgmproviderxpsp2up. MOF"

The output will look like below

Microsoft (r) 32-bit MOF compiler version 5.1.2600.2180
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: C: \ Program Files \ Microsoft SQL Server \ shared \ sqlmgmprovider
Xpsp2up. mof
MOF file has been successfully parsed
Storing data in the repository...
Done!

Note: The above mofcomp command is in the c: \ windows \ system32 \ WBEM directory. Some people use this method to solve the problem. I entered the Windows command processor and tried this method. I got the same output as him. I was very excited and thought the problem was solved. Log on to Server Configuration Manager again. Unfortunately, the same warning box is displayed. Continue searching on the Internet. Because most of the keywords are in English, in addition to the above method, the searched English webpage is a complaint ......

Next, I had to find a solution. I first thought about whether it was a problem with SQL Server 2005. Now that SQL Server 2008 Express is out, Install SQL Server 200. So uninstall SQL Server 2005 and Install SQL Server 2008 (installation is required before SQL Server 2008 is installed. net Framework SP2 and Windows Installer can be downloaded from the official Microsoft website. After installation, restart the computer). This installation is a Chinese version.

The Installation Process of SQL server 2008 is a little more difficult than that of SQL server 2005. You need to configure the database administrator and use the Administrator account of the local machine. After the installation is successful, enter the Configuration Manager with an uneasy mood. After clicking it, the damn warning box pops up again.

When I continue searching on the Internet, it is said that the administrator has no permissions for network service, so WMI cannot be enabled. The setting method is simple, and there are:

1. Right-click my computer and choose manage"
2. Double-click the Administrators group in "local users and groups". The add attribute dialog box is displayed.
3. Click Add. The Add User dialog box is displayed.
4. Click "advanced" and then "Search" (or "Search now. Note: The 'nt AUTHORITY \ NETWORK service' user is a built-in system account and cannot be added directly.

5. Select the "Network Service" user in "Search Results" and click "OK"

After completing the preceding settings, go to the Configuration Manager. The problem still persists ...... This is really depressing.

Now we can see a new method: Check whether framedyn exists in system32 in windows. if the system file dll is not copied to the wbem file in system32, framedyn. dll to the system32 directory. I went to the system32 directory to find the framedyn. dll file, and did not find it. Then I went to the system32 \ wbem directory, looked for framedyn. dll, and copied it to the system32 directory. Log on to the Configuration Manager again, and the configuration is successful this time !!! The problem is finally solved !!! This is mainly caused by problems with connecting to the database through Java or vc.

The above three methods always work on some computers. Unfortunately, I tried the third method to solve the problem. It is also possible that these three operations are required on my computer.