SQL Database Upgrade process-solve the WMI Service cannot be linked process, sqlwmi

SQL Database Upgrade process-solve the WMI Service cannot be linked process, sqlwmi

The trial period of the previously used SQL SERVER database is reached, and the database cannot be opened, prompting that the database has no permissions.

I believe many people have encountered this error, and there are also many solutions. You can find some preliminary work on the Internet.

Next let's talk about my solution: first understand what WMI is, which is taken from Baidu Encyclopedia: WMI, the core of Windows 2 K/XP management system; for other Win32 operating systems, WMI is a useful plug-in. WMI is based on CIMOM. CIMOM is the Common Information Model Object Manager. It is an Object database that describes the components of an operating system, provides a public interface for MMC and script programs to access the operating system components. With WMI, different APIs are not required when tool software and script programs access different parts of the operating system. On the contrary, WMI can be inserted into different parts of the operating system.

Step 2: Check whether the WMI service is enabled: win + R -- enter service. mrc, open the service -- find the WMI service -- and check whether the service is enabled.

Step 3: win + R -- Enter cmd -- enter mofcomp "C: \ Program Files (x86) \ Microsoft SQLServer \ 100 \ Shared \ sqlmgmproviderxpsp2up. mof (here is sqlmgmproviderxpsp2up in the shared folder under the installation directory of the SQL database. mof path. My shared path is under the 100 directory.) "-- press enter to run. If the problem is solved, congratulations. If the problem is not solved, go to step 4. The third step cannot be completed because it does not have the permissions of the Network Service user. Next, add the permissions to it.

Step 4: Right-click my computer-properties-advanced system settings-system properties-Environment Variables

Add the C: \ Windows \ System32 \ wbem path to path.

Step 2: Find framedyn. dll in the wben folder, right-click Properties> Security> edit under permission> Add> advanced> Search all> select NetworkService, and click OK.

Re-Execute Step 1 to obtain the following results:

Through comparison, the above failed result is the result before steps 4th and 5. After steps 4 and 5 are added, the correct result is obtained. Open the SQL Configuration Manager below:

It can be opened smoothly without so many troubles. This process is a complete conclusion.

My biggest achievement is to find a method and handle it according to your specific error. I searched for a long time on the Internet and found that the four methods are the same. At the beginning, I did the same operation according to the method, but it failed because framedyn is not in my wbem folder. dll files, which are the opposite of the errors mentioned on the Internet, and the shared folder under my SQL is under 100, and some solutions on the Internet are on 90 and on 110, they are not the correct solutions to their own problems. Through comparative analysis of these methods, we finally found that the solution is in line with our own method. This process also gives you confidence in solving problems and has accumulated experience.

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.