Hello, I get the following error, when trying to install SCCM client on Windows XP (SP3) machine. Any ideas? Thanks Angelo MSI: Setup was unable to compile the file SWDistEvents.mof The error code is 80041001 Angelo

Hi, That issue can be related to a WMI problem. Start the troubleshooting by using the WMIDiag tool http://www.microsoft.com/en-us/download/details.aspx?id=7684Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1

Concur. You may start troubleshooting with WMI. Also see WMI Troubleshooting Tips Sabrina TechNet Community Support

Hello, I used WMIDiag and got the output below, filtered for anything with "ERROR:". That is a good start so at least now I know what the errors are, but the question is how to go about fixing the problem. I looked at the documentation included but it talked more in general about what to do about WMI error. Can you recommend the best way to proceed? Is there a way to do a repair (similar to chksk /f) or maybe a way to easily rebuild WMI? Let me know what you think. Thanks 26775 17:50:04 (1) !! ERROR: (CheckWMIStaticData) : 0x80041001 - (WBEM_E_FAILED) Call failed. 26791 17:50:04 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'MIFPROV' DCOM registration data '{0362A876-DEED-41E2-9C43-88E5AE953288}' is missing or is access denied. 26801 17:50:06 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'FSINVPROV' DCOM registration data '{B982D155-CC99-41E6-AC31-C2A4EA3E5625}' is missing or is access denied. 26811 17:50:08 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'DDRINSTPROV' DCOM registration data '{49507317-AA1F-4FB2-B9EF-52BCF10D5A71}' is missing or is access denied. 27017 17:50:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ComputerSystem' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27029 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'ADSiteName' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27036 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_DiscoveryData' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27043 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_IPv6NetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27054 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ExtNetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27065 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_System' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27080 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_IPv6PrefixNetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27087 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'SMS_MIFGroup' still references the WMI Provider 'MIFPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27098 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_NetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27109 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ADSiteInfo' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 31419 17:51:45 (1) !! ERROR: (CheckWMIStaticData) : 0x80041001 - (WBEM_E_FAILED) Call failed. 34800 17:52:27 (1) !! ERROR: (CheckWMIProviderRegistration) : Unable to access or find WMI Provider EXE/DLL 'C:\WINDOWS\SYSTEM32\BCDPROV.DLL' (BCDPROV). 43292 17:55:08 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'MICROSOFT WMI TEMPLATE ASSOCIATION PROVIDER' DCOM registration data '{FD18A1B2-9E61-4E8E-8501-DB0B07846396}' is missing or is access denied. 48930 17:57:41 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 3 ERROR(S)! 48990 17:57:41 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 16 ERROR(S)! 49018 17:57:41 (1) !! ERROR: Unable to locate MOF file(s) in the WBEM folder or in Auto-Recovery list for the 49019 17:57:41 (1) !! ERROR: following CIM registered WMI provider(s): .................................................................... 5 ERROR(S)! 49041 17:57:41 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 24 FILE(S)! 49090 17:57:41 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR.PACIS.000\LOCAL SETTINGS\TEMP\WMIDIAG-V2.1_XP___.CLI.SP3.32_IPPA403_2012.04.30_17.40.50.LOG' for details. Angelo

Hello, I used WMIDiag and got the output below, filtered for anything with "ERROR:". That is a good start so at least now I know what the errors are, but the question is how to go about fixing the problem. I looked at the documentation included but it talked more in general about what to do about WMI error. Can you recommend the best way to proceed? Is there a way to do a repair (similar to chksk /f) or maybe a way to easily rebuild WMI? Let me know what you think. Thanks 26775 17:50:04 (1) !! ERROR: (CheckWMIStaticData) : 0x80041001 - (WBEM_E_FAILED) Call failed. 26791 17:50:04 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'MIFPROV' DCOM registration data '{0362A876-DEED-41E2-9C43-88E5AE953288}' is missing or is access denied. 26801 17:50:06 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'FSINVPROV' DCOM registration data '{B982D155-CC99-41E6-AC31-C2A4EA3E5625}' is missing or is access denied. 26811 17:50:08 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'DDRINSTPROV' DCOM registration data '{49507317-AA1F-4FB2-B9EF-52BCF10D5A71}' is missing or is access denied. 27017 17:50:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ComputerSystem' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27029 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'ADSiteName' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27036 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_DiscoveryData' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27043 17:51:11 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_IPv6NetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27054 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ExtNetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27065 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_System' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27080 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_IPv6PrefixNetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27087 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'SMS_MIFGroup' still references the WMI Provider 'MIFPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27098 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_NetworkAdapterConfiguration' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 27109 17:51:12 (1) !! ERROR: (CheckWMIClasses) : WMI Class 'CCM_ADSiteInfo' still references the WMI Provider 'DDRINSTPROV' in namespace 'ROOT/CCM/INVAGT', which has no DCOM registration data. 31419 17:51:45 (1) !! ERROR: (CheckWMIStaticData) : 0x80041001 - (WBEM_E_FAILED) Call failed. 34800 17:52:27 (1) !! ERROR: (CheckWMIProviderRegistration) : Unable to access or find WMI Provider EXE/DLL 'C:\WINDOWS\SYSTEM32\BCDPROV.DLL' (BCDPROV). 43292 17:55:08 (1) !! ERROR: (CheckWMIProviderRegistration) : WMI Provider 'MICROSOFT WMI TEMPLATE ASSOCIATION PROVIDER' DCOM registration data '{FD18A1B2-9E61-4E8E-8501-DB0B07846396}' is missing or is access denied. 48930 17:57:41 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 3 ERROR(S)! 48990 17:57:41 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 16 ERROR(S)! 49018 17:57:41 (1) !! ERROR: Unable to locate MOF file(s) in the WBEM folder or in Auto-Recovery list for the 49019 17:57:41 (1) !! ERROR: following CIM registered WMI provider(s): .................................................................... 5 ERROR(S)! 49041 17:57:41 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 24 FILE(S)! 49090 17:57:41 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\ADMINISTRATOR.PACIS.000\LOCAL SETTINGS\TEMP\WMIDIAG-V2.1_XP___.CLI.SP3.32_IPPA403_2012.04.30_17.40.50.LOG' for details. Angelo