≡ Menu

FIX: DFS Replication failed to register itself with WMI.

You might get alerts your DFS-R management pack in SCOM about the DFS-R service inability to register itself with WMI and it can impact the replication. Exact error message is given below.

DFS Replication failed to register itself with WMI. Replication is disabled until WMI registration succeeds.

To resolve this issue, you may need to re-register DFS-R related DLL and other files that belongs to WMI. Before going there, just restart your DFS-R service once to confirm that your problem is not transient and happening all time. You will notice a error message with 6104 event ID in DFS Replication event log after you restart the service. If this event is present, then problem is live and you should fix it.

The following solution worked for me.

CD %windir%\system32\wbem

mofcomp dfsrprov.mof

mofcomp dfsrprov.mfl

wmiprvse /regserver

net stop dfsr

net start dfsr

All it does is re-register the WMI related files of DFS-R.

If you still notice issues, you may want to re-register everything under WBEM folder. This was suggested in Technet Forum.

CD %windir%\system32\wbem
For /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s
for /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s
wmiprvse /regserver
net stop dfsr
net start dfsr

if the problem is still not resolved, try rebooting the DFS-R server.

Sometimes, the compilation of MOF files might fail with below errors while performing above steps. In such cases, http://support.microsoft.com/kb/841619 might help you.

C:\WINNT\system32\wbem>mofcomp dfsrprov.mof
Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.3959
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: dfsrprov.mof
MOF file has been successfully parsed
Storing data in the repository…
An error occurred while opening the namespace for object 1 defined on lines 4 –
4:
Error Number: 0x8007000e, Facility: Win32
Description: Not enough storage is available to complete this operation.
Compiler returned error 0x8007000e

A few more reference that might be useful for troubleshooting the issue:

  1. DFSR Does Not Replicate Temporary Files : http://blogs.technet.com/b/askds/archive/2008/11/11/dfsr-does-not-replicate-temporary-files.aspx
  2. http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/b8a8f0e6-9fcb-4a98-9951-bce109927dc8/

Thanks for reading my rambling. I wrote this for my quick reference and to help people who is searching for similar information.

WARNING: Above steps involves re-registration of WMI providers. So, test them in your lab and try in production at your own risk. I am not responsible for any damage that caused by above procedure.

Hope this helps…

 

{ 3 comments… add one }
  • Vijay May 18, 2016, 4:34 am

    sometime the below steps will fix this issue (DFS Replication service failed to register the WMI providers)

    1. Disable and stop the WMI service.
    sc config winmgmt start= disabled (note that there is a blank between ‘=’ and ‘disabled’)
    net stop winmgmt

    2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.

    3. Re-enable the WMI service.
    sc config winmgmt start= auto

    4. Reboot the server to see if the problem remains.

  • Vijay May 18, 2016, 4:36 am

    Try these steps (try it testing machine before implementing in production)
    1. Disable and stop the WMI service.
    sc config winmgmt start= disabled (note that there is a blank between ‘=’ and ‘disabled’)
    net stop winmgmt

    2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.

    3. Re-enable the WMI service.
    sc config winmgmt start= auto

    4. Reboot the server to see if the problem remains.

  • Vijay. B. Girija May 25, 2016, 1:06 am

    I followed the below steps for fixing the issue (DFS Replication service failed to register the WMI providers. Replication is disabled until the problem is resolved)
    Note – Please try these steps on test machine before implementing in production servers or any critical servers.
    1. Disable and stop the WMI service.
    sc config winmgmt start= disabled (note that there is a blank between ‘=’ and ‘disabled’)
    net stop winmgmt

    2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.

    3. Re-enable the WMI service.
    sc config winmgmt start= auto

    4. Reboot the server

Cancel reply

Leave a Comment