Message Tracking Center won't track messages
Hi Technet, I'm using Exchange 2003 SP2. Tried to use message tracking center but it gives me the error: " the search could not be completed. Check to see that the Microsoft Exchange Management service is running on all Exchange 2000 and Exchange 2003 installations." Verified that 1. WMI service is running 2. Exchange managment is running 3. Exchange services running using Local system account 4. Under exchange services > properties > log on > interact with desktop is unchecked. Looking at the message track log path, it contains the below error: "An error occurred during a call to Windows Management Instrumentation ID no: 80041013 Exchange System Manager" Any tips on how I can enable the message tracking?
February 3rd, 2010 8:16am

Hi Alex, Can you please check the the security settings of the WMI Control and compare the permissions with the other working Exchange servers. Run -> wmimgmt.msc Right-click on WMI Control (local) and select Properties -> Click on the Security tab-> Expand RootClick on a namespace, and then click on Security Button
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2010 11:14am

I actually only have 1 exchange server. So there isn't any for me to compare :P lol. Anyway. The WMI control settings for ROOT\WMI : Administrators all permission allowed, except for special permissions Everyone, Local Service and Network Service Allowed execute methods, Provider Write, Enable Account. ================ The message track log path becomes normal when the server is rebooted, but after a few moments it will return to the error "An error occurred during a call to Windows Management Instrumentation ID no: 80041013 Exchange System Manager" And in event vwr application log, we can see this event ===================== Event Type: Error Event Source: MSExchangeSA Event Category: General Event ID: 5007 Date: 04/02/2010 Time: 8:56:11 AM User: N/A Computer: MYKLX001 Description: An error occurred during the message tracking decode operation. error from file: f:\tisp2\admin\src\libs\rpc\rwlog.cxx line: 517. <<0xc0070842 - The Server service is not started.>> ===================== I have verified that the message tracking log share is there via "net share" Is this a problem with the WMI control permission?
February 4th, 2010 4:30am

I have checked the server service and started it. and now the event vwr app log error is gone. However I'm still seeing "An error occurred during a call to Windows Management Instrumentation ID no: 80041013 Exchange System Manager" in the exchange message track log path. Is the exchange services required to be restarted?
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 4:38am

Hi,Seems you have already check everything, please also have a look at this blog:http://www.computerperformance.co.uk/Logon/code/code_80041013.htmFrank Wang
February 4th, 2010 6:47am

Hi,The issue is related to WMI. Try running the following command from the location Windows\System32\Wbem to register WMI dlls.mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mofmofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\wbemcons.mof"mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\smtpcons.mof"mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\msgtrk.mof"Restart the Microsoft Exchange management service and WMI service.This should solve the issue.________________________Sanjay
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 7:46am

Can the Exchange managment and WMI service be restarted while the exchange server is running during production hours? i will try out registering the dlls :)
February 4th, 2010 9:29am

No,if you restart the WMI service the Exchange Services will be down for few seconds. Would suggest to register the dll files and restart the services during non-production hours._________________Sanjay
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2010 9:56am

Hello Alex,Take the registry backup.Got to the following registry location [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole] Create a string value “EnableRemoteDCOM" and assign the value “Y”.and reboot the machine and this should resolve the issue.Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
February 4th, 2010 11:33pm

Hi Alex,How about your question? Any update?Frank Wang
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2010 4:59am

Sorry Frank, haven't got a downtime for the exchange yet. can we keep this thread in pending while I try to register the dll on the server? Cheers.
February 8th, 2010 9:00am

Registering the DLLs resolved the issue. Thanks for the help
Free Windows Admin Tool Kit Click here and download it now
March 3rd, 2010 12:53pm

Dear Alex I am from kuwait , I have the same issue., and keep on coming in every 10 seconds. how can you solve without re-starting Exchange Event Type: ErrorEvent Source: MSExchangeSAEvent Category: General Event ID: 5007Date: 3/9/2010Time: 8:10:24 AMUser: N/AComputer: EXCHANGEDescription:An error occurred during the message tracking decode operation. error from file: f:\tisp2\admin\src\libs\rpc\rwlog.cxx line: 517. <<0xc0070842 - The Server service is not started.>> For more information, click http://www.microsoft.com/contentredirect.asp.
March 9th, 2010 10:04am

Hi Zienu,I actually registered the DLLs and restarted my exchange server in order to solve the problem I faced.BTW, for you problem, have you check the "Server" service whether it's started?
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2010 5:58am

Alex,"Server" service not started...shall I start this service..? Yesterday I have registered those DLL as per Mr. Sanjay's instruction and re-started the services, but i did not re-started the exchange server. Also today I find out that, message tracking is not working
March 11th, 2010 11:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics