Hi everyone, Winds Wu here. I had a case recently and found that Microsoft Windows Management Framework 3.0 (KB2506143) is not completely compatible with System Center 2007 Configuration Manager. The issue is that it may cause a reinstall of a Management Point to fail as you cannot compile mof files using the version of wmiutils.dll that is installed via KB2506143.
Here is the detailed information and workaround for your reference. If anything is unclear please feel free to let me know.
A Management Point failed to be installed and generated the following error in mpMSI.log:
[17:29:08] Failed to compile ‘E:\Program Files (x86)\SMS_CCM\LoggingDefaults.mof’ (Phase: 3, Object: 1, Lines: 21 – 29, Error: 80041002)
MSI (s) (38!40) [17:29:08:125]: Product: SMS Management Point — Error 25140. Setup was unable to compile the file LoggingDefaults.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file LoggingDefaults.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603
Analysis & Action Plan
1. We found that wmiutils.dll (under C:\Windows\System32\wbem) had the wrong version. It should be something similar to this which was what was on my server:
After checking with a WMI engineer, we found that it was probably caused by the hotfix in KB2506143 http://support.microsoft.com/kb/2506143 ). We already know there is another issue regarding this update in System Center 2012 Configuration Manager but it seems to affect Configuration Manager 2007 as well.
See KB2796086 (http://support.microsoft.com/kb/2796086) for more information.
To resolve the issue we uninstalled the update.
2. We then found that we could not compile LoggingDefaults.mof manually as it failed with the following error:
Microsoft (R) MOF Compiler Version 6.2.9200.16398
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: LoggingDefaults.mof
MOF file has been successfully parsed
Storing data in the repository…
An error occurred while resolving the alias for object 1 defined on lines 21 – 29:
0X80041002 Class, instance, or property ‘CCM_Logging_GlobalConfiguration’ was not found.
Compiler returned error 0x80041002
This occurred because some dependent mof files had not been compiled successfully. We checked the mpmsi.log from the working environment and saw that the compile sequence should be this:
To fix this we wrote a .bat file and compiled them one by one.
Once this was done, the only thing left to do was reinstall the Management Point. This time it was successful and we were good to go.
Winds Wu | Support Engineer | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/