Solved

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

Posted on 2011-02-20
5
1,201 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 

Author Comment

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

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 34948426
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
ID: 34975926
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
ID: 35005370
It worked
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Migration from Lotus Note to Exchange 4 27
Exchange 2007 6 19
Round robin for Exchange 2013 4 18
Cannot exit IF statement in PowerShell 4 17
Find out what you should include to make the best professional email signature for your organization.
In-place Upgrading Dirsync to Azure AD Connect
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

761 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