The visualsvnserver cannot be uninstalled or installed, and an invalid MOF file (0x80000001e) error is reported.

Document directory

• The solution

I encountered some trouble when I re-installed visualsvnserver yesterday. I will make up for it today.

 

The hard disk of this server (Windows Server 2003) has encountered a problem, and the faulty hard disk happened to be the hard disk installed by visualsvnserver. To reinstall visualsvnserver today, uninstall it first. However, when uninstallwmischemaexecute is executed, an error is reported: The MOF file is not valid (0x80000001e ). If it is re-installed, it will be automatically uninstalled and cannot be accessed. the download of the latest version is still the same.

 

So with the help of the network, Chinese search does not get effective help, then search English, find such a blog: http://rolf-engelhard.de /? P = 203, which is the same problem. The main steps are as follows:

The solution

1. Disable the WMI Service

   sc config winmgmt start= disabled  (make sure there is a blank between 'start' and 'disabled')

2. Stop the WMI Service

   net stop winmgmt

3. Go to % WINDIR %/system32/WBEM and rename the repository-Folder

   cd C:\WINDOWS\System32\wbem rename Repository Repository-old

4. Find the *. mof-file in % WINDIR %/system32/WBEM which belongs to visualsvn
   In my case the file was named "6e9a2709f6eb23a5e2f059acd767ad78. MOF ". inside there were multiple occurences of the string "visualsvn"-which I found by using notepad ++'s search-in-files-funktionality [2]. note that the Windows Search won't lead to any useable results since Windows doesn' t do a text-search on *. MOF-files by default.
5. Remove the file found in Step 4
6. Search the Registry on occurences of "visualsvn" and remove every found item
   I guess especially the key "autorecover mofs" in

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM

   Was an entry which recreated the faulty *. mof all over again.

7. Enabled the WMI Service

   sr config winmgmt start= auto

8. Start the visualsvn-Installation

 

In accordance with this step, it is indeed a good way to uninstall the software. However, there are two additional points:

1. If you want to be lazy in step 1, just delete the values related to visualsvnserver in the cimom key, but this does not work, so you have to honestly delete all values related to visualsvnserver from the registry;
2. It may be because the previous step has been deleted and the new version is installed. When an error occurs while starting the visualsvnserver service, the service cannot be started. In the control panel, I found that the visualsvnserver information is incorrect. In cmd, run the SC Delete visualsvnserver command to delete the entire service, and then install the software.