Hi expert ,

I ran into problem while trying to install SQL Server 2008 to join to another node in a failover cluster ,

you will find here the configuration doc and installation details

https://onedrive.live.com/redir?resid=D2927AF923DF3482!1270&authkey=!AM5PWhvOPo5vP3g&ithint=folder%2ctxt

Your support please.

i use MSSQL 2012 no service pack (sharepoint database) ,

 i have proprem error rbs 211 ,

so i want to update to sp3 ( Error when you run RBS Maintainer in SQL Server 2012 or SQL Server 2014   https://support.microsoft.com/en-us/kb/2979304)

can i update to 2012-->sp3  or update 2012-->sp1->sp2->sp3

best regards

chatchai-netd

We have 2 clustered SQL instances (2 physical servers in each cluster). Instance2 needs to be setup as a linked server on Instance1.

At this time port 1433 between them is not open. I am referring to the port on the network switch, not in the Windows Firewall (ports in Windows Firewall are already open).

Is opening the port between virtual IP-s sufficient? Or does port need to be open between all physical source/destination IP-s as well?

Hello All,

     I have a sql 2005 database on 2003, we are migrating this server over to 2008R2 as a clean install rather then an upgrade. I backuped up and moved over the databases as well as the logins and passwords. Everything works except one database that uses symmetric keys. I tried to create a master key for the database but it said one already existed. The symetic key already exists in the database, I can see it in SSMS. My question is how do I get the encryption working again. I have an ASP.NET application written on top of the database. It uses stored procedures in the database, they open the key as follows:

symmetrickey CP_Login_Keydecryptionbypassword='password'

my question is how do I get the encryption working again?

Hi,

I'm about to setup a new virtual machine, VMware, to run a SQL server 2012 installation.  My question is about setting up the underlying Windows server. 

I'm planning on using Windows server 2012 R2 and wondering what do I need to include in the server installation? 

What roles or features should I install or configure? 

Should I plan to install SQL server on the C: drive or a separate drive?

Should I plan to create the databases on the same drive as the SQL installation?  I am thinking of separating the database files from the log files on separate drives, which will be on separate LUNs in the storage array, if I can.  But would it be better to have the three components on separate drives, the SQL instance, the database files and the log files?

What else should I be considering that I haven't mentioned above?

Thanks in advance,

Linn

Hello there,

Please forgive my ignorance, this is the first time I have performed this procedure.

Essentially I am upgrading SQL Server Standard 2008 r2 to SQL Server Standard 2012, however I have a question concerning the licensing. Do I use the 2008r2 Product Key for the 2012 upgrade? Will I need to get a brand new SQL Server 2012 Standard Product Key? I believe that 2012 licensing now deals with logical cores and the VM that is hosting SQL Server 2012 Standard has 4 logical cores.

Someone told me that I shouldn't have to worry about spending money on additional licences because we have everything we need already, but I wanted to be reassured from the professionals.

Any help is obviously greatly appreciated.

Thanks,

Tom

 IN E.T.L ,MY QUERY IS GOING VERY LONG TIME , SO TABLE IS TRUNCATED EVERY DAY, I THINK SO TABLE DONT HAVE FREGNENTATION , SO HOW CAN SOLVE MY PROBLEM, I NEED TO INSERT DATA ORDER BY ?

  PLZ GIVE ME SOME ADVICE

THANK U

When trying to install SQL 2014 express on my W10 PC I get the error " Value cannot be Null. Parameter name: value". This seems to be during HKPerfCountersConfigAction_Repair_postmsi_Engine_Cpu64.  I can't see any way past this.  I have all Firewalls etc turned off.

Does anyone know what this issue might be?

SQL 2008R2 installs okay, but I can't use that on W10.

I have SQL Server 2008 R2 installed on Computer A. I want to remove it from Computer A and install it on Computer B. I have misplaced the original disk which I purchased for the install.

I presume I can download this product for the install on Computer B. I want it to be legitimate & licensed, though. Therefore, I want to locate the license or product key within the installed software or obtain it from Microsoft.

Alan

Hy,

some year ago, as a total newbie, I installed a server with a named instance. At that time I used a physical server, and moreover I probably  thought that SQL 2005 was the last version name for SQL server, so I named my instance with something like"hpserver\sql2005"...

Today I have a virtualized system, and I need to migrate SQL2005 to SQL 2014 (or 2016) and I would like to "rename" that instance.

The matter is that in last years more and more programs both with ODBC and ADO.NET connect to my server, and it's impossible to change all this programs in short time to connect to a new server.

My answer so is: it is possible to install a new server, named for example "ALPHA", and find some way to "redirect" all requests for older server to newest? I made some test and my matter is not (obviously) computer name, that I can mask with DNS, but instance name...

Hoping someone can help to correct my youth errors...

thanks

Mauro

I'm trying to install SQL server on my windows 7 workstation and got this error:

A MOF syntax error occured.

I looked in the SQL setup bootstrap folder and found the detail.txt. It says:

(01) 2015-11-29 19:23:58 Slp: Installing WMI Provider
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\110
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to get registry value SharedCode
(01) 2015-11-29 19:23:58 Slp: SharedDirPath is C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
(01) 2015-11-29 19:23:58 Slp: Attempting to install MOF/MFL file for WMI Provider C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to install MOF file
(01) 2015-11-29 19:23:58 Slp: Running: C:\Windows\system32\WBEM\mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"
(10) 2015-11-29 19:23:59 Slp: Microsoft (R) MOF Compiler Version 6.1.7600.16385
(10) 2015-11-29 19:23:59 Slp: Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
(10) 2015-11-29 19:24:00 Slp: Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(10) 2015-11-29 19:24:00 Slp: MOF file has been successfully parsed
(10) 2015-11-29 19:24:00 Slp: Storing data in the repository...
(10) 2015-11-29 19:24:03 Slp: An error occurred while processing item 10 defined on lines 73 - 79 in file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:
(10) 2015-11-29 19:24:03 Slp: Compiler returned error 0x80070005Error Number: 0x80070005, Facility: Win32
(10) 2015-11-29 19:24:03 Slp: Description: Access is denied.
(10) 2015-11-29 19:24:03 Slp:
(01) 2015-11-29 19:24:03 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:03 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:03 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:04 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-11-29 19:24:04 Slp: Inner exceptions are being indented
(01) 2015-11-29 19:24:04 Slp:
(01) 2015-11-29 19:24:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2015-11-29 19:24:04 Slp:     Message:
(01) 2015-11-29 19:24:04 Slp:         A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:     HResult : 0x84bb0001
(01) 2015-11-29 19:24:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2015-11-29 19:24:04 Slp:         ErrorCode : 1 (0001)
(01) 2015-11-29 19:24:04 Slp:     Data:
(01) 2015-11-29 19:24:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-11-29 19:24:04 Slp:       WatsonConfigActionData = INSTALL@CONFIGNONRC@COMMONFILES
(01) 2015-11-29 19:24:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-11-29 19:24:04 Slp:     Stack:
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: Watson Bucket 1
 Original Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : INSTALL@CONFIGNONRC@COMMONFILES

(01) 2015-11-29 19:24:04 Slp:
 Final Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : 0x4E91350D

(01) 2015-11-29 19:24:06 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:12 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:50 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:50 Slp: Watson bucket for exception based failure has been created
(01) 2015-11-29 19:38:42 Slp: Error: Action "Slp_Config_Install_Core_WMI_Provider_Cpu64" failed during execution.
(01) 2015-11-29 19:38:42 Slp: Completed Action: Slp_Config_Install_Core_WMI_Provider_Cpu64, returned False

How do I rectify this? Grateful for your advice.

Will installing another instance restart other instances?

Server is Windows Server 2012 R2, SQL Server is 2012.

Kind regards.

I recieved this error while installing sql server r2 :

An error occurred during the installation of assembly 'microsoft.vc80.CRT', Public Key Token="1fc8b3b9a1e18e3b", Type="Win32", Version="8.0.50727.762" HRESULT: 0x8007054F

I have created a .ini file with all my configuration settings for SQL Server 2008 R2. I need the application to install and not reboot automatically at the end as I am deploying it as a task sequence using MDT. 

How can I suppress the reboot at the end?

I was attempting to Install SQL 2014 on my Windows 10 (Pro) machine. The installation failed to install the engine, reporting services, analysis services.. it reported an "Invalid Driver" error as the cause... Going back to retry adding those features failed to work, as the setup tool reported them as installed..  So I went through the control panel and Uninstalled all the SQL server components ... now when I attempt to re-install SQL Server, I get to the step to specify the Instance name.. I'd prefer to continue to use the default "MSSQLSERVER" instance name, however the install fails, telling me that the instance name is already in use..

How can I remove the instance name ?  I uninstalled SQL Server already... ? how is the instance still registered as in use?

Jeff

I am fairly new to the failover clustering of servers and have somewhat been thrown in the mix. What I do know, we have a cluster consisting of two MS Windows Server 2008 R2 Enterprise (x64) physical servers running SQL Server 2008 SP1. We have, on each box, 3 different SQL instances running with a total of 50 databases that have been created. Not to get into to many details, I have a backup created from a SQL Server 2008 R2 SP1 that i cannot restore because the difference in versions which has led me to have to upgrade my version of SQL to match that of the backup.

What is my best course of action to upgrade this clustered environment with minimal faults?

Any and all help is appreciated and if I have left out anything pertinent please let me know. Thank you in advance for any advice. I do not wish to attempt to rush this process however management is always in a hurry.   

Hi,

I asked this qustion in the Windows Powershell section, but mabye someone here can point me in the right direction.

Here is the original thread:https://social.technet.microsoft.com/Forums/en-US/ee5ea1c6-1374-428f-8dec-fc6d4a4fd31c

I am trying to install SQL Server 2014 on a domain member server (server A) from a remote server within the same domain (server B). This is a simple lab setup consisting of just 1 DC and 2 member servers, so all domain settings are at their default setting. Setup files have been copied over to server A previously. I have attempted to use domain users and local users without success.

When the install is triggered through PowerShell from Server B, the install starts fine but after a few seconds I can see the following error in the log files:The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. The SQL summary log file is attached.

To work around the issue I have enabled “trust this computer for delegation to any service” in Active Directory on the computer and user object. However, this is not a practical solution. Is there a better way to solve this issue?

$credentials=Get-Credential(credentials are written in UPN format: administrator@lab.local)

$session=New-PSSession-ComputerName"serverA"-Credential$credentials

Invoke-Command-Session$session-ArgumentList"$sqlUser","$pw","$domain"-ScriptBlock {

                          param (

                                  [Parameter(Mandatory=$true, Position= 1)]

                                  [string]$sqlUser,

                                  [Parameter(Mandatory=$true, Position= 2)]

                                  [string]$pw,

                                  [Parameter(Mandatory=$true, Position= 3)]

                                  [string]$domain

                           )

$sqlInstance="MSSQLSERVER”

C:\SQL\Setup.exe /Q /UpdateEnabled="False" /ACTION="Install" /FEATURES="SQLEngine, RS, IS, Tools" /SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" /SQLSYSADMINACCOUNTS="$domain\Administrator" /IACCEPTSQLSERVERLICENSETERMS="True" /INSTALLSQLDATADIR="D:\$sqlInstance" /SQLBACKUPDIR="D:\$sqlInstance\Backup" /SQLUSERDBDIR="D:\$sqlInstance\Data" /SQLUSERDBLOGDIR="E:\$sqlInstance\Log" /SQLTEMPDBDIR="F:\$sqlInstance\Tempdb" /SQLTEMPDBLOGDIR="E:\$sqlInstance\Log" /SAPWD="123456" /SECURITYMODE="SQL" /INSTANCENAME="$sqlInstance" /INSTANCEID="$sqlInstance" /SQLSVCACCOUNT="$domain\$sqlUser" /SQLSVCPASSWORD="$pw" /SQLSVCSTARTUPTYPE="Automatic" /AGTSVCACCOUNT="$domain\$sqlUser" /AGTSVCPASSWORD="$pw" /AGTSVCSTARTUPTYPE="Automatic" /RSSVCACCOUNT="$domain\$sqlUser" /RSSVCPASSWORD="$pw" /RSINSTALLMODE="FilesOnlyMode"

}

Here is the SQL Summary Log:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068774911
  Exit facility code:            1201
  Exit error code:               1
  Exit message:                  There was an error generating the XML document.
  Start time:                    2015-12-01 15:14:42
  End time:                      2015-12-01 15:15:28
  Requested action:              Install
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xE0C083E6%400xB2215DAC&EvtType=0xE0C083E6%400xB2215DAC

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.


Machine Properties:
  Machine name:                  ServerA
  Machine processor count:       1
  OS version:                    Windows Server 2012
  OS service pack:
  OS region:                     Norge
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\SQL\x64\setup\
  Installation edition:          Standard

Product Update Status:
  User selected not to include product updates.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 LAB\__labsql28
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, RS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             D:\MSSQLSERVER
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:
  RSINSTALLMODE:                 FilesOnlyMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  LAB\__labsql28
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  D:\MSSQLSERVER\Backup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 LAB\__labsql28
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           LAB\500000-T15-DBA
  SQLTEMPDBDIR:                  F:\MSSQLSERVER\Tempdb
  SQLTEMPDBLOGDIR:               E:\MSSQLSERVER\Log
  SQLUSERDBDIR:                  D:\MSSQLSERVER\Data
  SQLUSERDBLOGDIR:               E:\MSSQLSERVER\Log
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151201_151440\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Reporting Services - Native
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Integration Services
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools SDK
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Setup Support Files
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity SDK
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Writer
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Documentation Components
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Browser
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151201_151440\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
    Message:
        There was an error generating the XML document.
    HResult : 0x84b10001
        FacilityCode : 1201 (4b1)
        ErrorCode : 1 (0001)
    Data:
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(Object objectToSerialize)
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CalculateSettings(IEnumerable`1 settingIds)
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CalculateAllSettings(Boolean chainerSettingOnly)
        at Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    Inner exception type: System.InvalidOperationException
        Message:
                There was an error generating the XML document.
        HResult : 0x80131509
        Stack:
                at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
                at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)
                at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        Inner exception type: System.Security.Cryptography.CryptographicException
            Message:
                        The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

            HResult : 0x80090345
            Stack:
                        at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
                        at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)
                        at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write6_AgentConfigurationPublic(String n, String ns, AgentConfigurationPublic o, Boolean isNullable, Boolean needType)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write7_AgentConfigurationPublic(Object o)

I'm trying to install SQL server on my windows 7 workstation and got this error:

A MOF syntax error occured.

I looked in the SQL setup bootstrap folder and found the detail.txt. It says:

(01) 2015-11-29 19:23:58 Slp: Installing WMI Provider
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\110
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to get registry value SharedCode
(01) 2015-11-29 19:23:58 Slp: SharedDirPath is C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
(01) 2015-11-29 19:23:58 Slp: Attempting to install MOF/MFL file for WMI Provider C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to install MOF file
(01) 2015-11-29 19:23:58 Slp: Running: C:\Windows\system32\WBEM\mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"
(10) 2015-11-29 19:23:59 Slp: Microsoft (R) MOF Compiler Version 6.1.7600.16385
(10) 2015-11-29 19:23:59 Slp: Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
(10) 2015-11-29 19:24:00 Slp: Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(10) 2015-11-29 19:24:00 Slp: MOF file has been successfully parsed
(10) 2015-11-29 19:24:00 Slp: Storing data in the repository...
(10) 2015-11-29 19:24:03 Slp: An error occurred while processing item 10 defined on lines 73 - 79 in file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:
(10) 2015-11-29 19:24:03 Slp: Compiler returned error 0x80070005Error Number: 0x80070005, Facility: Win32
(10) 2015-11-29 19:24:03 Slp: Description: Access is denied.
(10) 2015-11-29 19:24:03 Slp:
(01) 2015-11-29 19:24:03 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:03 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:03 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:04 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-11-29 19:24:04 Slp: Inner exceptions are being indented
(01) 2015-11-29 19:24:04 Slp:
(01) 2015-11-29 19:24:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2015-11-29 19:24:04 Slp:     Message:
(01) 2015-11-29 19:24:04 Slp:         A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:     HResult : 0x84bb0001
(01) 2015-11-29 19:24:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2015-11-29 19:24:04 Slp:         ErrorCode : 1 (0001)
(01) 2015-11-29 19:24:04 Slp:     Data:
(01) 2015-11-29 19:24:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-11-29 19:24:04 Slp:       WatsonConfigActionData = INSTALL@CONFIGNONRC@COMMONFILES
(01) 2015-11-29 19:24:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-11-29 19:24:04 Slp:     Stack:
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: Watson Bucket 1
 Original Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : INSTALL@CONFIGNONRC@COMMONFILES

(01) 2015-11-29 19:24:04 Slp:
 Final Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : 0x4E91350D

(01) 2015-11-29 19:24:06 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:12 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:50 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:50 Slp: Watson bucket for exception based failure has been created
(01) 2015-11-29 19:38:42 Slp: Error: Action "Slp_Config_Install_Core_WMI_Provider_Cpu64" failed during execution.
(01) 2015-11-29 19:38:42 Slp: Completed Action: Slp_Config_Install_Core_WMI_Provider_Cpu64, returned False

How do I rectify this? Grateful for your advice.