Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. System Center Configuration Manager 2007 does not install, and a "Failed to compile MOF" error is logged

System Center Configuration Manager 2007 does not install, and a "Failed to compile MOF" error is logged

Symptoms

When you try to install Microsoft System Center Configuration Manager 2007, the installation fails, and the Manage Object Format (MOF) files are not compiled. You see an entry in the Configmgrsetup.log file that resembles the following:
<Date_&_Time> CompileMOFFile: Failed to compile MOF D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\smsRprt.mof, error -2147217407

<Date_&_Time> Setup cannot compile MOF file D:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\smsRprt.mof. Do you want to continue?

<Date_&_Time> Setup failed to install SMS Provider. For more information about this error, see Microsoft Knowledge Base at http://microsoft.com or contact Microsoft Technical Support for further assistance.
Additionally, you may see an entry in the Mofcomp.log file that resembles the following:
(Date_&_Time) : Parsing MOF file: C:\Program Files\Microsoft Configuration Manager\bin\i386\smsRprt.mof

(Date_&_Time) : An error occurred while processing item 1 defined on lines 7 - 32 in file C:\Program Files\Microsoft Configuration Manager\bin\i386\smsRprt.mof:

(Date_&_Time) : Error Number: 0x80041013, Facility: WMI

Description: Provider load failure (Date_&_Time) : Compiler returned error 0x80041001(Date_&_Time) : Parsing MOF file: C:\Program Files\Microsoft Configuration Manager\bin\i386\sms_schm.mof

↑ Back to the top

Cause

This issue occurs when the installation program for Configuration Manager 2007 cannot communicate with a remote computer that is running Microsoft SQL Server. This occurs when the service principal names (SPN) attributes on the SQL Server are not generated for the service account that started the SQL services, and the SPNs do not use a domain user account.

↑ Back to the top

Resolution

To resolve this issue, you must correctly configure the SPNs for the SQL Server to use the correct domain user account. For more information about how to do this, visit the following Microsoft TechNet webpage:
How to Configure an SPN for SQL Server Site Database Servers
Additionally, you should verify that there are no duplicate SPNs on the SQL Server. For more information about how to detect duplicate SPNs, download the following document from this Microsoft website:
Microsoft CRM 3.0: Additional Setup Tasks Required if Reporting Services Is Installed on Different Server
Note Download the document, and then locate the "Make sure SPNs are not already used on any Active Directory forest" section.

↑ Back to the top

More Information

For more information about Configuration Manager 2007 installation, visit the following TechNet blog:
The Configuration Manager Service Pack Install Guide

↑ Back to the top

Keywords: kb, kbeventlog, kbsetup, kbinstallation, kbpubtypekc, kbtshoot, kbsurveynew, kbprb

↑ Back to the top

Article Info
Article ID : 2384060
Revision : 2
Created on : 4/10/2020
Published on : 4/10/2020
Exists online : False
Views : 140