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.
posted by jamestechman at 6:47 AM
13 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!
Post a Comment
<< Home