Link to home
Start Free TrialLog in
Avatar of Shawna_Parker
Shawna_Parker

asked on

The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'.

After fixing a WMI problem that required deleting the WMI Repository, I have started to receive this error on my Windows 2003 Exchange Server, which is running on a Windows 2003 SBS server.

Is there a way to fix the WMI without reinstalling Exchange entirely?
ASKER CERTIFIED SOLUTION
Avatar of marc_nivens
marc_nivens

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Shawna_Parker
Shawna_Parker

ASKER

Thanks for responding to my issue so quickly.

When i type in the first command, i get an error message saying that the file exwmi.mof is not found.
Did the other commands work?  If none of them worked make sure you are in the system32\wbem folder when you run them.  If its just the first one that failed you should be able to copy exwmi.mof from the installation CD.
sorry, you already addressed this. I will get the missing file from the cd.
I finally got to the right directory, and also double-checked that the file exwmi.mof was in the Windows\system32\wbem folder, but when i run the command, the system prompts me for a program to run the files.
mofcomp.exe prompts you for a program?  
Yes. when i am in the ...\wbem directory and type mofcomp exwmi.mof i am prompted for a program
Try typing mofcomp.exe exwmi.mof instead.  Maybe specifying the EXE extension will get past this problem.
I get a prompt that says Windows cannot open the file exwmi.mof and asks for a program association to open the file
There must be some other issues going on with this install because thats definitely not supposed to happen.  Perhaps the WMI rebuild caused it, maybe not.  If it were my machine I'd probably use filemon/regmon to troubleshoot further (you can get these tools from www.sysinternals.com).  They're a bit hard to get at first but they log every registry and file access attempt and usually prove useful with wierd issues like this one.  You could run them while you run the mofcomp command and see what its doing behind the scenes thats making it act up.
I am going to try installing SP2 and see if that solves it. Otherwise i will try the tools you suggest. Thanks again for your help.