• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1221
  • Last Modified:

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

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
itnorthservice
Asked:
itnorthservice
  • 3
1 Solution
 
itnorthserviceAuthor Commented:
Thanks Chris I was having difficulty with adding to topic areas when I posted.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
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
 
itnorthserviceAuthor Commented:
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
 
itnorthserviceAuthor Commented:
It worked
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now