Search WWW Search

Saturday, July 08, 2006

Exchange: Message Tracking Corrupted Produces Error message "ID no: 8004100e Exchange System Manager",


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.


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.


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
mofcomp.exe -n:root\cimv2\applications\exchange
mofcomp.exe -n:root\cimv2\applications\exchange

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)
Security+, Project+, ITIL

How useful was this article? Want to see a tip not listed? Please leave a comment.


Anonymous Anonymous said...

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!

9:42 PM  
Blogger jamestechman said...

Glad it helped!

12:28 PM  
Anonymous Anonymous said...

Cheers James, this has helped me out too

2:04 AM  
Anonymous Anonymous said...

Absolutely magic. Thanks for a great resource!

8:19 PM  
Anonymous Anonymous said...

I just followed your cookbook and presto! The error is gone. Thank you for an excellent tip.

12:03 PM  
Anonymous Anonymous said...

Thank you very much for the one and only hint on the internet that really worked

8:21 AM  
Anonymous Anonymous said...

Thanks for that it worked as described. If only all help could be so accurate.

9:59 PM  
Anonymous Anonymous said...

James - thanks for this -worked first time on my W2K3 SBS server. Saved me bags of time figuring it out...

1:38 AM  
Anonymous Anonymous said...

Thanks - Worked by my exchange 2000 box. Just had to change the Windows to WINNT in the paths! Great Blog!!

10:55 AM  
Anonymous Anonymous said...

Thanks, fixed it on a Win SBS 2003

3:14 PM  
Anonymous Anonymous said...

Wow! It really worked. Used this method on my Win2K and it worked :)

5:28 AM  
Anonymous Anonymous said...

Many thanks for this - worked a treat!

2:20 AM  
Anonymous Anonymous said...

Great Job! Worked like a change. Thanks so much for the documentation!

7:41 PM  
Blogger Ph. said...

Great Works again !

Thanks !!!

7:32 AM  
Blogger balaji said...

fantastic man it worked.. :)

5:29 AM  
Anonymous Anonymous said...

darn, didnt work for me, can find the file applications/exchange

7:31 AM  
Blogger longge said...

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.

6:48 PM  
Anonymous Anonymous said...

You are the master! It worked great!

6:46 AM  
Anonymous Anonymous said...

Thanks! Very helpful advice

3:11 AM  
Anonymous Anonymous said...

Thanks! :)

12:24 AM  
Anonymous Neels said...

It worked for me as well SBS 2003

7:04 AM  
Anonymous Anonymous said...

Been pulling my hair out over this one. Thank you ever so much for your great advice it fixed the problems right away :)

5:06 AM  
Anonymous Anonymous said...

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

3:30 PM  
Anonymous Anonymous said...


1:56 AM  
Anonymous Anonymous said...

Thanks very much!

12:36 AM  
Blogger Simple Luxury said...

Burberry Outlet Store Online
Handbags Outlet Store Online
Louis Vuitton Handbags Sale

11:18 AM  
Blogger Lamont said...

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.

10:18 AM  
Anonymous aqui said...

Goodness, there's so much effective information here!

6:12 AM  
Anonymous Anonymous said...

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!

12:08 PM  
Blogger Brian Downs said...

THANK YOU!!!! After many years this has fixed my issue!!!

1:49 PM  
Blogger aalia lyon said...

Nice blog click this link and get a perfect solution .
BOOTMGR Missing in Windows 7
Thank you
Aalia lyon

2:05 AM  
Blogger dong dong said...

christian louboutin
oakley sunglasses cheap
christian louboutin outlet
hollister clothing store
ray ban outlet
louis vuitton outlet stores
christian louboutin sale
michael kors bag
cheap lululemon
michael kors outlet online sale
true religion outlet
coco chanel
michael kors handbags
ray ban glasses
red christian louboutin
louis vuitton handbags
michael kors outlet online
coach outlet store online
rolex watches outlet
celine outlet
ray ban sunglasses
cheap jordans
coach factory outlet
jordan 13
hollister clothing
tory burch outlet online
oakley vault
jordan shoes
mont blanc
toms outlet
nfl jerseys

12:46 AM  
Blogger Meiqing Xu said...

louis vuitton outlet
michael kors handbags
beats by dr dre
jordan concords
michael kors outlet
fitflop shoes
coach factory outlet online
michael kors outlet
hermes birkin bag
football shoes
louis vuitton handbags
new jordans
retro 11
chanel outlet
hollister kids
michael kors bag
true religion jeans
michael kors outlet online
christian louboutin outlet
longchamp outlet
louis vuitton outlet
kate spade outlet
michael kors
louis vuitton handbags
tods outlet store
prada outlet
oakley sunglasses
louis vuitton
fake oakleys
louis vuitton
louis vuitton handbags
abercrombie outlet
sac longchamp pas cher
ray bans
true religion
pandora jewelry
chanel bags
michael kors outlet

6:55 PM  

Post a Comment

<< Home

xml:lang="en" lang="en"> MS Exchange Tips: Exchange: Message Tracking Corrupted Produces Error message "ID no: 8004100e Exchange System Manager",