September 24, 2013 at 10:43 am
Hi,
SQl cluster 2008 r2 failed with below error.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: Failed: see details below
Start time: 2013-09-24 18:02:40
End time: 2013-09-24 18:34:10
Requested action: InstallFailoverCluster
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: xxxxxxxxxxxA
Machine processor count: 24
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: Yes
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xD3BEBD98@1211@1
Configuration error description: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\Detail.txt
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130924_175452\SystemConfigurationCheck_Report.htm
Kindly help me to find out the error.........
September 25, 2013 at 6:47 am
Looks like this isn't an uncommon problem. Here are a couple of links to go through that might help:
http://sql.nconsulting.net/2012/10/installation-error-mof-compiler-could.html#.UkLaLtXD-Hs
Please note I have not experienced this issue, but these links seem to include some possible solutions.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply