Solved

Missing top level Class "exchange_messagetrackingentry" from WMI root\microsoftExchangeV2

Posted on 2011-02-20
5
1,182 Views
Last Modified: 2012-05-11
Hello All
Ok so this from a Windows 2003 SBS server running Exchange 2003 SP2.  I was first seeing errors when I would go to message tracking : “An error occurred during a call to Windows Management Instrumentation ID no: 80041010 Exchange System manager”
After research I found a few articles on the matter and how to possibly fix it by re installing Exchange Management Service and reregistering DLL’s etc... http://groups.google.com/group/microsoft.public.windows.server.sbs/msg/4eb7e7729a26f600  
However after performing this I was still seeing the same issue.  After what I did was run WBEMTEST.EXE to check the classes on a working Windows 2003 SBS and cross referenced the two Enum Classes and found that the class “Exchange_MessageTrackingEntry      (CIM_LogicalElement)” is missing from the server with the issue.
As I’m not a 100% familiar with WMI classes etc... and am pretty sure this is related to my issue of message tracking not working I need help on how to get that restored or I guess how to manualy re-add that class?

Much appreciated
0
Comment
Question by:itnorthservice
  • 3
5 Comments
 

Author Comment

by:itnorthservice
Comment Utility
Thanks Chris I was having difficulty with adding to topic areas when I posted.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
Comment Utility
Once you start messing with manually readding things like this you get into all sorts of trouble.  Your best bet would be to first run the SBS Best Practices analyzer (http://sbsurl.com/bpa)

Then run the Exchange 2003 BPA found here:  http://www.microsoft.com/downloads/en/details.aspx?familyid=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en

You will probably get a lot of issues that need resolution from running those two tools.  

You also can try reinstalling Exchange 2003 SP2 which can help to fix minor issues.

Jeff
TechSoEasy
0
 

Accepted Solution

by:
itnorthservice earned 0 total points
Comment Utility
As per Microsoft.
According to the information, I suspect that the issue may happen because the mentioned WMI class is missing. So I would like to confirm: Have you re-register the .mof files? If not, please first run the following command at a Command Prompt and then verify the issue.

 

mofcomp -n:root\cimv2\applications\exchange C:\Windows\System32\Wbem\msgtrk.mof

Thanks
0
 

Author Closing Comment

by:itnorthservice
Comment Utility
It worked
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
A procedure for exporting installed hotfix details of remote computers using powershell
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now