Exchange: Message Tracking Corrupted Produces Error message "ID no: 8004100e Exchange System Manager",
Summary:
You receive error message "ID no: 8004100e Exchange System Manager", when you are using the Message Tracking Center or in the field where you enter the Path to store The Message Tracking Logs through ESM.
Cause:
The error code 8004100e translates to WBEM_E_INVALID_NAMESPACE, which means the failure is due to an invalid namespace or a corrupted CIM Repository.
Resolution:
To resolve this issue, you will need to attempt registration of the
necessary DLLs and to import the Exchange Namespaces and Classes. Running the below commands will harm nothing if the DLLs are already registered or if the Namespaces and/or Classes are already present in the WMI Repository. I have written a batch file that will automate the process below which you can download from "Chong Man's Exchange Resources" under links and going to the Scripts directory.
1. Run the following command from a command prompt in the Program Files\Exchsrvr\Bin directory:
regsvr32 /s exwmi.dll
regsvr32 /s cdowf.dll
regsvr32 /s cdowfevt.dll
2. Run the following commands from a command prompt in the
Windows\System32\Wbem directory:
mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof
mofcomp.exe C:\WINDOWS\system32\WBEM\exwmi.mof
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\wbemcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\smtpcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\msgtrk.mof"
3. Restart the Windows Management Instrumentation service and all related services.
If the issue still persists, the files in the %SystemRoot%\System32\Wbem\Repository folder may get corrupted. Run these steps:
1. Click Start, and then right-click My Computer.
2. On the shortcut menu, click Manage.
3. In the left pane of the Computer Management console, double-click “Services and Applications".
4. Under "Services and Applications", click Services.
5. In the right pane of the Computer Management console, locate and then
right-click Windows Management Instrumentation.
6. On the shortcut menu, click Stop.
7. Start Windows Explorer, and then locate the
%SystemRoot%\System32\Wbem\Repository folder.
8. Copy %SystemRoot%\System32\wbem\Repository to a different folder and then delete all of the files in the %SystemRoot%\System32\Wbem\Repository folder.
9. Register all DLLS in %SystemRoot%\System32\wbem. To do so, run the following commands:
cd C:\WINDOWS\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
10. Restart the computer. The files that were deleted are re-created when
the computer restarts as the Windows Management Instrumentation service
starts automatically when you restart the computer.
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+
Security+, Project+, ITIL
msexchangetips.blogspot.com
How useful was this article? Want to see a tip not listed? Please leave a comment.
You receive error message "ID no: 8004100e Exchange System Manager", when you are using the Message Tracking Center or in the field where you enter the Path to store The Message Tracking Logs through ESM.
Cause:
The error code 8004100e translates to WBEM_E_INVALID_NAMESPACE, which means the failure is due to an invalid namespace or a corrupted CIM Repository.
Resolution:
To resolve this issue, you will need to attempt registration of the
necessary DLLs and to import the Exchange Namespaces and Classes. Running the below commands will harm nothing if the DLLs are already registered or if the Namespaces and/or Classes are already present in the WMI Repository. I have written a batch file that will automate the process below which you can download from "Chong Man's Exchange Resources" under links and going to the Scripts directory.
1. Run the following command from a command prompt in the Program Files\Exchsrvr\Bin directory:
regsvr32 /s exwmi.dll
regsvr32 /s cdowf.dll
regsvr32 /s cdowfevt.dll
2. Run the following commands from a command prompt in the
Windows\System32\Wbem directory:
mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof
mofcomp.exe C:\WINDOWS\system32\WBEM\exwmi.mof
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\wbemcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\smtpcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange
"C:\WINDOWS\system32\wbem\msgtrk.mof"
3. Restart the Windows Management Instrumentation service and all related services.
If the issue still persists, the files in the %SystemRoot%\System32\Wbem\Repository folder may get corrupted. Run these steps:
1. Click Start, and then right-click My Computer.
2. On the shortcut menu, click Manage.
3. In the left pane of the Computer Management console, double-click “Services and Applications".
4. Under "Services and Applications", click Services.
5. In the right pane of the Computer Management console, locate and then
right-click Windows Management Instrumentation.
6. On the shortcut menu, click Stop.
7. Start Windows Explorer, and then locate the
%SystemRoot%\System32\Wbem\Repository folder.
8. Copy %SystemRoot%\System32\wbem\Repository to a different folder and then delete all of the files in the %SystemRoot%\System32\Wbem\Repository folder.
9. Register all DLLS in %SystemRoot%\System32\wbem. To do so, run the following commands:
cd C:\WINDOWS\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
10. Restart the computer. The files that were deleted are re-created when
the computer restarts as the Windows Management Instrumentation service
starts automatically when you restart the computer.
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+
Security+, Project+, ITIL
msexchangetips.blogspot.com
How useful was this article? Want to see a tip not listed? Please leave a comment.
36 Comments:
Thank you, your tip was very helpful. After restore DC w2k with Exchange 2000 by Backup Exec on another hardware and eseutil on MailboxStores, it was applicable but Message Tracking Center produses 8004100e. After registering WMI components it works!
Glad it helped!
Cheers James, this has helped me out too
Absolutely magic. Thanks for a great resource!
I just followed your cookbook and presto! The error is gone. Thank you for an excellent tip.
Thank you very much for the one and only hint on the internet that really worked
Thanks for that it worked as described. If only all help could be so accurate.
James - thanks for this -worked first time on my W2K3 SBS server. Saved me bags of time figuring it out...
Thanks - Worked by my exchange 2000 box. Just had to change the Windows to WINNT in the paths! Great Blog!!
Thanks, fixed it on a Win SBS 2003
Wow! It really worked. Used this method on my Win2K and it worked :)
Many thanks for this - worked a treat!
Great Job! Worked like a change. Thanks so much for the documentation!
Great Works again !
Thanks !!!
fantastic man it worked.. :)
:)
darn, didnt work for me, can find the file applications/exchange
The replica handbags design debuted in 1888. replica handbags uk design was launched in an effort to counteract the replicas his competitors were marketing. replica bags was made of an intersection of the initials LV, finished with a curved beige diamond and 4 point star intes.
You are the master! It worked great!
Thanks! Very helpful advice
Thanks! :)
It worked for me as well SBS 2003
Been pulling my hair out over this one. Thank you ever so much for your great advice it fixed the problems right away :)
Following your guide resolved the issue on our 2003 SBS running Exchange.
Thank you for your really helpful guide. It is much appreciated.
Alan Ayres
Perfecte!
Thanks very much!
Markus
Thanks, I performed a restore test of our 2 AD's and 2 Exchange2003 servers running on Windows Server 2003 Standard.Your fixed the WMI on the Exchange servers. thanks.
Goodness, there's so much effective information here!
Bravo! Its work for me also. I was working on this issue since long time but today I solved this issue with the help of your article. Thanks. Thanks a ton!
THANK YOU!!!! After many years this has fixed my issue!!!
toms shoes, supra shoes, montre pas cher, ugg uk, juicy couture outlet, moncler, lancel, michael kors outlet online, ugg pas cher, michael kors handbags, barbour, doke & gabbana, michael kors outlet, coach outlet, louis vuitton uk, canada goose jackets, pandora charms, moncler, ugg,ugg australia,ugg italia, links of london uk, moncler jackets, hollister, juicy couture outlet, canada goose outlet, swarovski uk, pandora jewelry, canada goose pas cher, canada goose outlet, marc jacobs, moncler pas cher, thomas sabo uk, swarovski jewelry, karen millen uk, louis vuitton, moncler, moncler uk, sac louis vuitton, canada goose, moncler outlet, louis vuitton, canada goose, wedding dresses uk, ugg,uggs,uggs canada, canada goose uk, sac louis vuitton, moncler, replica watches, barbour jackets uk, bottes ugg pas cher, canada goose jackets
true religion outlet
ugg outlet
nike blazer
michael kors outlet
michael kors bags
new orleans saints jerseys
ugg outlet
armani exchange
ugg boots
ralph lauren
2017.7.29
fitflops
chrome hearts
brady jersey
adidas yeezy
michael kors outlet
adidas shoes
lacoste polo
chrome hearts
nike air max
jordan shoes
zzzzz2018.7.14
nike presto
jordan shoes
moncler jackets
coach outlet online
ralph lauren outlet
canada goose jackets
mbt shoes outlet
cheap snapbacks
christian louboutin sale
moncler online
Continue to Perbiki his blog to get a good blog !!
Cara Mengobati Jamur Mulut
Cara Mengobati Telinga Berair
Pengobatan Epilepsi Dengan Bahan Alami
Cara Mengobati Rematik
Pengobatan Berbagai Macam Luka Sampai Tuntas
Pengobatan Penyakit Kanker Payudara Tanpa Operasi
Awesome read
I got the same error message but now gone.
Post a Comment
<< Home