Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2384060 - Last Review: November 16, 2010 - Revision: 1.0
System Center Configuration Manager 2007 does not install, and a "Failed to compile MOF" error is logged
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
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.
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:
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:
Note Download the document, and then locate the "Make sure SPNs are not already used on any Active Directory forest" section.
For more information about Configuration Manager 2007 installation, visit the following TechNet blog:
APPLIES TO
- Microsoft System Center Configuration Manager 2007
| kbprb kbsurveynew kbtshoot kbpubtypekc kbinstallation kbsetup kbeventlog KB2384060 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate