Article ID: 2387686 - Last Review: May 18, 2011 - Revision: 5.0 FIX: "A MOF syntax error occurred" error message occurs when you try to install SQL Server 2008 or SQL Server 2008 R2
Microsoft distributes Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 or SQL Server 2008 R2 fix release. On This PageSYMPTOMSWhen you try to install SQL Server 2008 or SQL Server 2008 R2, the installation fails. Additionally, you receive an error message that resembles the following: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839 Exit facility code: 1203 Exit error code: 1 Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup. Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100513_122519\Detail.txt Configuration error code: 0xD3BEBD98@1211@1 Configuration error description: A MOF syntax error occurred. <Time Stamp> Slp: An error occurred while processing item 183 defined on lines 18232 - 18447 in file E:\MSSQL10\MSSQL10.MSSQLSERVER\MSSQL\Binn\etwcls.mof.transformed:
<Time Stamp> Slp: Compiler returned error 0x800706beError Number: 0x800706be, Facility: Win32 <Time Stamp> Slp: Description: The remote procedure call failed. <Time Stamp> Slp: <Time Stamp> Slp: Sco: Compile operation for mof file E:\MSSQL10\MSSQL10.MSSQLSERVER\MSSQL\Binn\etwcls.mof.transformed failed. Exit code 3 <Time Stamp> Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC. <Time Stamp> Slp: A MOF syntax error occurred. <Time Stamp> Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC. <Time Stamp> Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred. CAUSEThis issue occurs because of a compilation error in the Etwcls.mof.transformed MOF file during Setup. RESOLUTIONThis hotfix only provides a partial fix for this MOF compilation issue. To completely resolve this issue, you must also apply hotfix 2446036. Hotfix 2446036 resolves all possible failures with MOF compilation of any MOF file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2446036
(http://support.microsoft.com/kb/2446036/
)
FIX: You cannot install SQL Server 2008 or SQL Server 2008 R2 after you apply CU9 for SQL Server 2008 SP1 Cumulative update informationSQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2083921
(http://support.microsoft.com/kb/979065/LN/
)
Cumulative update package 9 for SQL Server 2008 Service Pack 1 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:970365
(http://support.microsoft.com/kb/970365/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2289254
(http://support.microsoft.com/kb/2289254/
)
Cumulative update 1 for SQL Server 2008 Service Pack 2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:2402659
(http://support.microsoft.com/kb/2402659/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:2345451
(http://support.microsoft.com/kb/2345451/
)
Cumulative Update package 4 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
