Sql Server 2012 Clustering ?
Dear Friends, I want to configure clustering for SQL Server 2012 on windows 2008 R2 Sp2. I have two big questions:
1) Domain controller configuration is mandatory for SQL Server clustering?
2) Please share any link "if possible share best one"
Hopes you will support.
Regards
Irfan Ahmad
Hi Irfan_Lhr,
You post same question 3 times.Please avoid this practice on Forum, I have merged the same threads .
When you setup VM/host for cluster, you require installing Windows Operating System in nodes and Domain Controller. And domain controller is necessary because of domain environment. About SQL Server clustering, for setting up domain environment, you should
do the following things.
•Installing Active Directory on Domain Controller;
•Setting up DNS Server;
•Joining Cluster Nodes in Domain Environment.
You also need to note if there are no pre-existing Active Directory when you can deploy cluster nodes in an environment, there is detail about
how to configure at least one of the cluster nodes as a domain controller.
There is videos about setting up SQL Server 2008 cluster on Windows 2008, you can review them.
http://www.sqlserver-training.com/sql-server-2008-clustering-on-windows-2008-video-2/-
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support
Similar Messages
-
Creating a windows cluster 2012 for sql server 2012 clustered installation
Hello,
I am trying to create a windows cluster for sql server 2012 clustering on windows server 2012 R2 standard edition-64bit OS
when i perform the test after adding the cluster nodes i get this warning on networking.:Validate the servers can communicate
do i have to enable UDP port 1434?
I enabled ports 3343 on both the server but i still get the error.Please see the image below .Please suggest.
Thank you.
luckyDo you have installed one SQL Server instance on the node?
http://blogs.technet.com/b/meamcs/archive/2013/02/15/sql-2012-failover-cluster-build-step-by-step-part-1-installing-sql-2012.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence -
SQL Server 2012 - Clustered installation fails - cannot locate MSIs
Hi forum
I have a query relating to SQL Server 2012 installation, on Windows Server 2012 R2 - SQL Server is Enterprise, Windows is SQL Server Standard Edition.
Our windows team have created two Windows Server 2012 machines, and installed and got cluster services running.
We've tried the installation of SQL Server 2012 RTM, slipstream SP1 and slipstream SP2, and all come up with an error during the installation - I've even tried the trial version of SQL Server 2012 (SP1), just in case there is a media issue.
Immediately after the window which it is installing the installation files, we get the error:
SQL Server Setup has encountered the following error:
Failed to retrieve data for this request.
You'll see in the logfile of the installation below, that the installer cannot locate specific MSI files
e.g.
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\x64\sql_fulltext.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\x86\sql_fulltext.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\x64\sql_dq.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\x86\sql_dq.msi' does not exist
I've expanded and checked the ISO / IMG files and these files do not exist.
I'd suspect media corruption, however, the installer works fine on a stand-alone machine, and the same files are missing from two separate sets of installation media - so I think that rules it out.
If someone could give us a clue over what the problem is, we'd really appreciate it - we're trying to create a 2012 availability group setup, so need cluster services...
Many thanks
Carl.
LOGFILE:-----------------------------------------------------------------------------------------------------------
(01) 2015-03-02 11:29:12 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2015-03-02 11:29:12 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2015-03-02 11:29:13 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2015-03-02 11:29:13 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2015-03-02 11:29:13 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2015-03-02 11:29:13 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:13 Slp: Running Action: ReadProductXML
(01) 2015-03-02 11:29:13 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2015-03-02 11:29:13 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2015-03-02 11:29:13 Slp: Completed Action: ReadProductXML, returned True
(01) 2015-03-02 11:29:13 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:13 Slp: Running Action: LoadExtensions
(01) 2015-03-02 11:29:13 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'MSI' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'PackageChainer' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.PackageChainerExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'PackageChainer' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'Config' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'Common' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'SqlConfigBase' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'Slp' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'RulesEngine' version '11.0.5058.0' loaded
Truncated due to limitations of posting
(01) 2015-03-02 11:29:13 Slp: Extension 'FulltextConfig' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'ScoExtension' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.ScoExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'ScoExtension' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'Infrastructure' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Chainer.Infrastructure.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'Infrastructure' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'UtilityConfig' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.UtilityExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'UtilityConfig' version '11.0.2100.60' loaded
(01) 2015-03-02 11:29:13 Slp: Loading extension 'SmartSetup' from file 'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\x64\.\Microsoft.SqlServer.Configuration.SmartSetupExtension.dll'
(01) 2015-03-02 11:29:13 Slp: Extension 'SmartSetup' version '11.0.5058.0' loaded
(01) 2015-03-02 11:29:13 Slp: Completed Action: LoadExtensions, returned True
(01) 2015-03-02 11:29:13 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:13 Slp: Running Action: ExecuteBootstrapAfterExtensionsLoaded
(01) 2015-03-02 11:29:14 Slp: Workflow to execute: 'BOOTSTRAPAFTEREXTENSIONSLOADED'
(01) 2015-03-02 11:29:14 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:14 Slp: Running Action: SetGlobalPackageFlags
(01) 2015-03-02 11:29:14 Slp: Completed Action: SetGlobalPackageFlags, returned True
(01) 2015-03-02 11:29:14 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:14 Slp: Running Action: LoadPackageDatastoreObjects
(01) 2015-03-02 11:29:14 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettings.xsd'
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettingsDefaults.xml'
(01) 2015-03-02 11:29:14 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettings.xsd'
loaded into datastore path '/Datastore/InputSettings/ChainerSettings/SlpSettings'
(01) 2015-03-02 11:29:14 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettings.xsd'
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SlpFeatureInputSettingDefaults.xml'
Truncated due to limitations of posting
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml'
(01) 2015-03-02 11:29:14 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd' loaded into datastore
path '/Datastore/ProductSettings/ClusterNode/Public'
(01) 2015-03-02 11:29:14 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd'
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml'
(01) 2015-03-02 11:29:14 Slp: Document 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd' loaded
into datastore path '/Datastore/ProductSettings/SQLServerSCP/Private'
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml'
(01) 2015-03-02 11:29:14 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml' loaded into datastore path '/Datastore/ProductSettings/ClusterNodesStatus/Public'
(01) 2015-03-02 11:29:14 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd'
(01) 2015-03-02 11:29:14 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml'
(01) 2015-03-02 11:29:14 Slp: Document 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd' loaded into datastore
path '/Datastore/ProductSettings/ASSIP/Public'
(01) 2015-03-02 11:29:14 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
(01) 2015-03-02 11:29:14 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:14 Slp: Running Action: InitializeInputSettingStore
(01) 2015-03-02 11:29:15 Slp: Completed Action: InitializeInputSettingStore, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: InitializeRoleService
(01) 2015-03-02 11:29:15 Slp: Loading role: SPI_AS_NewFarm
(01) 2015-03-02 11:29:15 Slp: Loading role: SPI_AS_ExistingFarm
(01) 2015-03-02 11:29:15 Slp: Loading role: AllFeatures_WithDefaults
(01) 2015-03-02 11:29:15 Slp: Completed Action: InitializeRoleService, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: ProcessChainerCommandLineArguments
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: WORKFLOW
(01) 2015-03-02 11:29:15 Slp: Value specified: INSTALL
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: TIMESTAMP
(01) 2015-03-02 11:29:15 Slp: Value specified: 20150302_112838
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: LOGMARKER
(01) 2015-03-02 11:29:15 Slp: Value specified:
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: MEDIASOURCE
(01) 2015-03-02 11:29:15 Slp: Value specified: E:\
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: INSTALLMEDIAPATH
(01) 2015-03-02 11:29:15 Slp: Value specified: E:\x64\setup\
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: ENU
(01) 2015-03-02 11:29:15 Slp: Value specified: True
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: MEDIALAYOUT
(01) 2015-03-02 11:29:15 Slp: Value specified: Full
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: ACTION
(01) 2015-03-02 11:29:15 Slp: Value specified: INSTALL
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: CUPIDDISPLAYED
(01) 2015-03-02 11:29:15 Slp: Value specified: FALSE
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: PID
(01) 2015-03-02 11:29:15 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: ProcessMediaChainerConfigFileArguments
(01) 2015-03-02 11:29:15 Slp: Procssing media configuration file E:\x64\setup\..\DefaultSetup.ini.
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Setting: PID
(01) 2015-03-02 11:29:15 Slp: New setting source: ConfigFile; previous setting source: CommandLine. The previous setting values were preserved.
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------
(01) 2015-03-02 11:29:15 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: ProcessChainerConfigFileArguments
(01) 2015-03-02 11:29:15 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: ProcessSlipstreamParameters
(01) 2015-03-02 11:29:15 Slp: Completed Action: ProcessSlipstreamParameters, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
(01) 2015-03-02 11:29:15 Slp: Action is being skipped due to the following restrictions:
(01) 2015-03-02 11:29:15 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: InitializeRetryHandler
(01) 2015-03-02 11:29:15 Slp: Completed Action: InitializeRetryHandler, returned True
(01) 2015-03-02 11:29:15 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:15 Slp: Running Action: ValidateChainerSetting
(01) 2015-03-02 11:29:15 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:15 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:15 Slp: -- PidInfoProvider : Compute new PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Read lcid 1033 from CultureInfo
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: Completed Action: ValidateChainerSetting, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ProcessFeatureCommandLineArguments
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------
(01) 2015-03-02 11:29:16 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
(01) 2015-03-02 11:29:16 Slp: Procssing media configuration file E:\x64\setup\..\DefaultSetup.ini.
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------
(01) 2015-03-02 11:29:16 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ProcessFeatureConfigFileArguments
(01) 2015-03-02 11:29:16 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: StartSqmSession
(01) 2015-03-02 11:29:16 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-03-02 11:29:16 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\110
(01) 2015-03-02 11:29:16 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2015-03-02 11:29:16 Slp: SQM Service: Sqm does not have active session.
(01) 2015-03-02 11:29:16 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
(01) 2015-03-02 11:29:16 Slp: Completed Action: StartSqmSession, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ValidateSettingsAgainstScenario
(01) 2015-03-02 11:29:16 Slp: Scenario: Install
(01) 2015-03-02 11:29:16 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: FinalCalculateSettings
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2015-03-02 11:29:16 Slp: -- PidInfoProvider : Use cached PID
(01) 2015-03-02 11:29:16 Slp: Completed Action: FinalCalculateSettings, returned True
(01) 2015-03-02 11:29:16 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: SetInstallScenarioFlags
(01) 2015-03-02 11:29:16 Slp: Completed Action: SetInstallScenarioFlags, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ExecuteInitWorkflow
(01) 2015-03-02 11:29:16 Slp: Workflow to execute: 'STANDARDTOPLEVELINIT'
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: SetStandardTopLevelScenarioFlags
(01) 2015-03-02 11:29:16 Slp: Completed Action: SetStandardTopLevelScenarioFlags, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: ExecuteUpdateInitWorkflow
(01) 2015-03-02 11:29:16 Slp: Workflow to execute: 'InitializeUpdateSearch'
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: SetJobId
(01) 2015-03-02 11:29:16 Slp: Completed Action: SetJobId, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: AddSmartSetupEnginesAction
(01) 2015-03-02 11:29:16 Slp: Registered update search engine 'SfxcabSearchEngine'
(01) 2015-03-02 11:29:16 Slp: Registered update search engine 'SlipstreamSearchEngine'
(01) 2015-03-02 11:29:16 Slp: Registered update search engine 'MuSearchEngine'
(01) 2015-03-02 11:29:16 Slp: Registered update download engine 'MuDownloadEngine'
(01) 2015-03-02 11:29:16 Slp: Registered update extract engine 'SfxcabExtractEngine'
(01) 2015-03-02 11:29:16 Slp: Completed Action: AddSmartSetupEnginesAction, returned True
(01) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:16 Slp: Running Action: RunSmartSetupWorkflow
(09) 2015-03-02 11:29:16 Slp: ----------------------------------------------------------------------
(09) 2015-03-02 11:29:16 Slp: Running Action: SearchUpdatesAction
(09) 2015-03-02 11:29:17 Slp:
(09) 2015-03-02 11:29:17 Slp: Microsoft Update Details:
(09) 2015-03-02 11:29:17 Slp: Category ID searched on Microsoft Update: 7fe4630a-0330-4b01-a5e6-a77c7ad34eb0
(01) 2015-03-02 11:29:17 Slp: Completed Action: RunSmartSetupWorkflow, returned True
(01) 2015-03-02 11:29:17 Slp: Completed Action: ExecuteUpdateInitWorkflow, returned True
(01) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:17 Slp: Running Action: ExecuteInitWorkflow
(01) 2015-03-02 11:29:17 Slp: Workflow to execute: 'INITIALIZATION'
(01) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:17 Slp: Running Action: AddPackageEnginesAction
(01) 2015-03-02 11:29:17 Slp: Completed Action: AddPackageEnginesAction, returned True
(01) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:17 Slp: Running Action: AddPackageInstallerEnginesAction
(01) 2015-03-02 11:29:17 Slp: Completed Action: AddPackageInstallerEnginesAction, returned True
(01) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(01) 2015-03-02 11:29:17 Slp: Running Action: InitializeMsiExtension
(09) 2015-03-02 11:29:17 Slp: Major version of the Windows Update Agent: 8
(09) 2015-03-02 11:29:17 Slp: Minor version of the Windows Update Agent: 0
(09) 2015-03-02 11:29:17 Slp: Version of Wuapi.dll:
7.9.9600.17489
(09) 2015-03-02 11:29:17 Slp:
(09) 2015-03-02 11:29:17 Slp: Completed Action: SearchUpdatesAction, returned True
(09) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(09) 2015-03-02 11:29:17 Slp: Running Action: PackageDownloadAction
(09) 2015-03-02 11:29:17 Slp: Completed Action: PackageDownloadAction, returned True
(09) 2015-03-02 11:29:17 Slp: ----------------------------------------------------------------------
(09) 2015-03-02 11:29:17 Slp: Running Action: PackageExtractAction
(09) 2015-03-02 11:29:17 Slp: Completed Action: PackageExtractAction, returned True
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_runtime_lp_32_Cpu32_1033 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_runtime_lp_32_Cpu32_1053 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_runtime_lp_64_Cpu64_1033 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_runtime_lp_64_Cpu64_1053 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_designtime_lp_Cpu32_1033 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_vsta_designtime_lp_Cpu32_1053 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_VSHelpLP_Cpu64_1033 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_VSHelpLP_Cpu64_1046 and directory SystemDrive
(01) 2015-03-02 11:29:17 Slp: SLP: MsiExtension.GetDiskCost: Warning: No matched disk size is detected for feature ALL_VSHelpLP_Cpu64_1053 and directory SystemDrive
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\sql_engine_core_inst_msi\x64\sql_engine_core_inst.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\x64\setup\sql_engine_core_inst_msi\x86\sql_engine_core_inst.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1028_CHT_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1028_CHT_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1031_DEU_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1031_DEU_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1036_FRA_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1036_FRA_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1040_ITA_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1040_ITA_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1041_JPN_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1041_JPN_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1042_KOR_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msi' does not exist
(01) 2015-03-02 11:29:18 Slp: Sco: File 'E:\1042_KOR_LP\x64\setup\sql_engine_core_inst_loc_msi\sql_engine_core_inst_loc.msi' does not exist
Truncated due to limitations of posting
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2015-03-02 11:29:20 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
(01) 2015-03-02 11:29:20 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Failed to retrieve data for this request. ---> Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve
data for this request. ---> Microsoft.SqlServer.Configuration.Sco.SqlRegistryException: The network path was not found.
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.CreateBaseKey(ServiceContainer ctx, String machineName, IntPtr hKey, String keyName, RegistryAccess access, RegistryView view)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocalMachine(ServiceContainer ctx, String machineName, RegistryAccess access, RegistryView view)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineRootKey(ServiceContainer ctx, String machineName, RegistryView registryView)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2015-03-02 11:29:20 Slp: --- End of inner exception stack trace ---
Truncated due to limitations of posting
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName,
RegistryView regView)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
(01) 2015-03-02 11:29:20 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)Hello,
What the summary.txt log file says? Could you share the content of that file with us?
Have you tried to copy the media to a local drive, unzip the ISO file into a folder and run SQL Server setup from there.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Unable to set (ssl) certificate on a SQL Server 2012 clustered instance
Hello everyone!
I'm trying to encrypt the SQL Server communication with SSL but I can't add the certificate in the configuration manager. I've found and tried a lot of different explaination but none of them worked. I'll described what I've done and hope someone will point
out what I'm missing.
Here is my situation:
- SQL Server 2012 Enterprise Edition. Instance name = INSTANCE, FQDN = SQINSTANCE.mydomain.com. The instance is running under a customized service account: mydomain\sql_sa
- Two cluster nodes running Win Server 2008R2: NODE1.mydomain.com and NODE2.mydomain.com. Cluster itself is CLUSTER.mydomain.com
What I've done:
1) Asked the team in charge to generate a certificate issued to "SQINSTANCE.mydomain.com" with aliases to "NODE1.mydomain.com", "NODE2.mydomain.com" and "CLUSTER.mydomain.com". I get a certificate with "p7b"
as extension
2) Connect on "NODE2.mydomain.com" with account "mydomain\sql_sa". Opened MMC and added the certificate under "Personnal" folder. I tried to add it with "Current user" and "Local computer" settings. Saw both
on internet since I use a specific service account
3) Get the thumbprint of the certificate and add it under HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL11.INSTANCE\MSSQLServer\SuperSocketNetLib\Certificate. (I triple checked to remove blanks or special characters)
4) Reboot the node
5) Open the SQL Server Configuration Manager, go to the network properties. Certificate does not appear in the list
I tried to check with certutil and saw the certificate in the output. Some guys talked about some private key but I don't see this particularity in my situation. I tried to check if the certificate is valid and, according to the criterias, it is.
Does anyone can help me with this?Hi,
Are you sure you've got the certificate correct? http://msdn.microsoft.com/en-us/library/ms191192.aspx
To use encryption with a failover cluster, you must install the server certificate with the fully qualified DNS name of the virtual server
on all nodes in the failover cluster. For example, if you have a two-node cluster, with nodes named test1.<your
company>.com and test2.<your
company>.com, and you have a virtual server named virtsql, you need to install a certificate for virtsql.<your
company>.com on both nodes. You can set the value of the ForceEncryptionoption
toYes
In your case, shouldn't it be created for CLUSTER.mydomain.com?
Thanks, Andrew
My blog... -
Can SQL server 2014 instance be introduced into SQL server 2012 clustering
Hello, everyone,
We have SQL server clustering set up in place (it is actually windows clustering), I am wondering if it is possible to introduce SQL server 2014 instance
into this clustering. Please share us your thoughts and experiences.
Thanksif you are talking about SQL clustering -(FAILOVER CLUSTERED INSTANCES) , yes, you can do that.
you have windows cluster with nodea,nodeb....and you can install two different instances of failover clustered sql - sql 2012 and sql 2014.
Hope it Helps!! -
All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
GmanIn general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim -
SQL Server 2012 Multi-Site clustering with 2 nodes for HA and DR
Usually we setup 2 Node Prod cluster for Local HA and 1 or 2 Nodes in other data centre for DR
Given that we have an option to setup multi-site / multi-subnet clustering from SQL 2008 R2/2012. I am planning to use just 2 nodes, 1 in prod data centre and 1 in DR data centre with 2 or 3 instances. This will act as both HA and DR solution.
I would like to know if this solution is good, and any disadvantages, any best practices, etc.? By implementing this I can save some cost on physical servers.
Following will be configured:
* Will be using different subnets, quorum on different server with "Node and File Share Majority"
* All virtual IPs will be registered for virtual name, and Subnetdelay, Subnet threshold will be modified accordingly
* All nodes on same domain
* Use SAN Disk with replication to DR siteSQL 2008 R2 doesn't support multi-subnet clustering. You would still need 3rd party component like VLAN and Disk Replication. SQL 2012 is the first version to support multi-subnet clustering without using VLAN. you would still need disk replication hardware/software.
Taken from my book
Since nodes are often located in two different data centers at geographically dispersed locations, there is no shared storage between the nodes in a multi-site cluster. Clustering across two different data centers provides a higher level of availability and
protection at the storage level as we have more than a single copy of the data.
For SAN replication technology implemented in such clusters, the main activity is to keep data replicated between the sites. Typically, if we have nodes on two different sites, we would have two different network infrastructures and the nodes would be in
different subnets. In such cases, if we are on a SQL Server version before 2012, we need to use third party VLAN (Virtual LAN) technology so that one IP address travels between two sites. This is called wide-IP. Companies hesitate with this solution because
of the need to buy a third party solution to deploy the VLAN. Using VLAN technology means the same IP address would failover to the remote site in case of a local site disaster. Network administration might consider this as an overhead to maintenance and an
extra piece of the networking component that needs to be secure.
With SQL Server 2012 we do not need to use stretch VLAN technology but SAN replication is still needed for multi-site clustering. The OS version for this can be from Windows Server 2008 R2 and above. In this deployment, we can have a SQL virtual network
name having an “OR” dependency on two different IP addresses. One address would be representing each subnet. With the “OR” dependency, if IP1 or IP2 is online we just use the network name. This is one of the Enterprise Editions only features.
Other option which you can think of, without using 3rd party solutions would be AlwaysOn Availability Group. I have written details about it in my book.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle -
Unable to install SQL server 2012 on windows 7 64bit
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2057043966
Exit facility code: 1380
Exit error code: 2
Exit message: There was a failure to calculate the applicability of setting ALLINSTANCES.
Start time: 2015-03-17 21:43:13
End time: 2015-03-17 21:43:34
Requested action: LandingPage
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x4F2D2386%400xE9BC3D64&EvtType=0x4F2D2386%400xE9BC3D64
Machine Properties:
Machine name: ELKR-1214-1745
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\afaeb7739e47ceedb4b5f79a1e14a784\x64\setup\
Installation edition:
User Input Settings:
ACTION: LandingPage
CONFIGURATIONFILE:
ENU: true
HELP: false
INDICATEPROGRESS: false
QUIET: false
QUIETSIMPLE: false
UIMODE: AutoAdvance
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150317_214254\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
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.CalculateSettingApplicabilityException
Message:
There was a failure to calculate the applicability of setting ALLINSTANCES.
HResult : 0x85640002
FacilityCode : 1380 (564)
ErrorCode : 2 (0002)
Data:
SettingId = ALLINSTANCES
WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
HelpLink.EvtType = 0x4F2D2386@0xE9BC3D64
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
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.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingChangeabilityException
Message:
There was a failure to calculate the changeability of setting ALLINSTANCES.
HResult : 0x85640003
FacilityCode : 1380 (564)
ErrorCode : 3 (0003)
Data:
SettingId = ALLINSTANCES
WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingChangeabilityException@3
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateChangeabilityByUser()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.UnableRetrieveConfigObjectForSettingException
Message:
Unable to retrieve a public configuration object type Microsoft.SqlServer.Configuration.SetupExtension.SlpInputSettings for setting ALLINSTANCES.
HResult : 0x85640007
FacilityCode : 1380 (564)
ErrorCode : 7 (0007)
Data:
SettingId = ALLINSTANCES
ConfigObjectType = Microsoft.SqlServer.Configuration.SetupExtension.SlpInputSettings
WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.UnableRetrieveConfigObjectForSettingException@7
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.SettingBridge.GetHostingObject()
at Microsoft.SqlServer.Chainer.Infrastructure.SettingBridge.ChangeabilityByUser()
at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateChangeabilityByUser()
Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
Message:
Unable to generate a temporary class (result=1).
error CS0009: Metadata file 'c:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll' could not be opened -- 'File is corrupt'
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type)
at Microsoft.SqlServer.Chainer.Infrastructure.SettingBridge.GetHostingObject()
Inner exception type: System.InvalidOperationException
Message:
Unable to generate a temporary class (result=1).
error CS0009: Metadata file 'c:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll' could not be opened -- 'File is corrupt'
Stack:
at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)Hi,
I would like to add that if you see summary.txt file you would see
Message:
Unable to generate a temporary class (result=1).
error CS0009: Metadata file 'c:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll' could not be opened -- 'File is corrupt'
HResult : 0x84b10001
FacilityCode : 1201 (4b1)
ErrorCode : 1 (0001)
You can see file is corrupt. So either you have to download the setup file again or there can be chance that Antivirus caused some issue.
Plus if you see starting of summary.txt you could see
Requested action: LandingPage
The error message came while landing page was being loaded/or was in action so again I think it is some thing related to corrupt media or antivirus.
Please
1. Download ISO file again and extract using WINRAR, don't use Winzip
2. Disable Antivirus.
3. Make a new folder and extract installable there.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS
Another user,
Cheer08, has replied to a thread you have subscribed to in the
SQL Server Express Forum.
Here are the error messages:
Error 2
Error 1
Hello,
This error is related to Microsoft Visual C++ 2005. Could you try to download and install Microsoft Visual C++ 2005 with service pack 1 (SP1) included:
http://www.microsoft.com/en-us/download/details.aspx?id=5638 (x86 or 32-bit)
http://www.microsoft.com/en-us/download/details.aspx?id=18471
(x64 or 64-bit)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thread Title Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS.
Started by: FenixRising
Reply:
Fenix, this is SQL Server forum. Regarding the Visual C++ 2005 SP1 Redistributable setup issue, you need to post question in
visual studio forum to get better help.
After installing Visual C++ 2005 SP1 Redistributable successfully,are you able to install SQL Server? If not, share us SQL Server setup logs. This link
https://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx will help you View and Read SQL Server Setup Log Files
Im going to run it now. Get back to you.Hi,
I am unable to install SQL Server 2012. I have the install log, but I don't can't read them.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2053898239
Start time: 2015-02-08 23:03:01
End time: 2015-02-08 23:07:31
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: RLC_WORK
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
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
SQL Server 2012
Client Tools Connectivity 1033
11.2.5058.0 No Yes
SQL Server 2012
Client Tools Backwards Compatibility 1033
11.2.5058.0 No Yes
SQL Server 2012
Client Tools SDK 1033
11.2.5058.0 No Yes
SQL Server 2012
SQL Server Data Tools 1033 Express Edition
11.2.5058.0 No Yes
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\76766b629842c4dc54646a47c04202\x64\setup\
Installation edition: Express
Slipstream: True
SP Level 2
Product Update Status:
Success: KB 2958429
Product Updates Selected for Installation:
Title: Service Pack 2
Knowledge Based Article: KB 2958429
Version: 11.2.5058.0
Architecture: x64
Language: 1033
Update Source: Slipstream
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
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: true
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RLC_WORK\Robert
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: Slipstream
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft .NET Framework 3.5
Component error code: 0x85940001
Error description: Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\SystemConfigurationCheck_Report.htm
Fenix -
Rule "SQL Server 2012 feature Upgrade" Failed
I am doing an in-place upgrade of SQL Server 2008 R2 SP2 > SQL Server 2012 SP1, both 64-bit, installed on Windows Server 2008 R2.
I ran the SQL Server Upgrade Advisor tool prior to upgrade which reported no issues.
The error I am getting is:
In the detailed.txt log I can see the following:
(11) 2013-12-29 12:28:10 Slp: Initializing rule : SQL Server 2012 Feature Upgrade
(11) 2013-12-29 12:28:10 Slp: Rule is will be executed : True
(11) 2013-12-29 12:28:10 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Found feature package 'sql_as_ctp6_Cpu64' with SkuValue=ENTERPRISE (Enterprise) ProductVersion=10.52.4000.0
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition ENTERPRISE for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=STANDARD (Standard) targetArchitecture=X64
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
(11) 2013-12-29 12:28:10 Slp: Evaluating rule : FeatureUpgradeMatrixCheck
(11) 2013-12-29 12:28:10 Slp: Rule running on machine: TAUPE-SERVER
(11) 2013-12-29 12:28:10 Slp: Rule evaluation done : Failed
(11) 2013-12-29 12:28:10 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
(11) 2013-12-29 12:28:10 Slp: Send result to channel : RulesEngineNotificationChannel
Prior to upgrade:
From Summary.txt file:
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2013-12-29 12:04:28
End time: 2013-12-29 12:08:02
Requested action: RunRules
Machine Properties:
Machine name: TAUPE-SERVER
Machine processor count: 1
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: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services - Native
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity 1033 Enterprise Edition 10.52.4000.0
No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition: Standard
Slipstream: True
User Input Settings:
ACTION: RunRules
CONFIGURATIONFILE:
ENU: true
FEATURES:
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: <empty>
PID: *****
QUIET: false
QUIETSIMPLE: false
RULES: GlobalRules
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\SystemConfigurationCheck_Report.htm
As far as I'm aware, the upgrade path I am following is a supported one, any suggestions will be much appreciated!
Thank you.Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services - Native
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity 1033 Enterprise Edition 10.52.4000.0
No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition: Standard
Slipstream: True
User Input
Hello ,
You are trying to upgrade to SQL 2012 standard edition which is not supported .you can only upgrade from SQL server 2008 R2 Sp2 Enterprise edition to SQL 2012 Enterprise or business intellgience. see below link for supported upgrade paths
http://technet.microsoft.com/en-us/library/ms143393.aspx
If you want to move ahead you should try Side by side approach.Create new SQL server 2012 box and restore backup.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Full-Text search is not working with PDF files - SQL Server 2012 64 bit
Hi,
We are in the process of storing PDF files in SQL Server 2012 with Full-Text search capability.
I followed the steps as below and it works fine with word document but not for PDF files. I tried with PDF ifiler 11 & 9 and both are unsuccessful.
Server/DB Level Settings:
1)
Enable FileStream
2)
Install Full-Text
then restart
3)
Use [specific db]
alter
database [db name]
add
filegroup Files
contains filestream;
alter
database [db name]
add
file (
name = N'Files',
filename =
N'D:\SQL\DATA') to
filegroup [Files];
3)
Database level
Settings:
FileStream:
FileStream
Directory name:
[Set the name]
FileStream
non-transacted
Access: [set Appropriate]
3a)
Add a
datafile to DB
with filestreamdata
filetype.
4)
Share D:\SQL\DATA
directory and
add specific accounts
with read/write
access
5)
Give bulkadmin
access to those
specific accounts
at server
level
6)
From the
page (link)
download and
install the *.pdf
IFilter for
FTS. Link:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5542
7)
To the
PATH global system
variable add
path to the
catalog,
where you installed
the plugin.
Default for
this version is:
C:\Program
Files\Adobe\Adobe
PDF iFilter 9
for 64-bit
platforms\bin
8)
From the
page (link)
download a
FilterPackx64.exe
and install
it. Link:
http://www.microsoft.com/en-us/download/confirmation.aspx?id=20109
9)
Now from
SSMS execute the following
procedures:
-sp_fulltext_service
'load_os_resources',1
-sp_fulltext_service
'verify_signature', 0
EXEC
sp_fulltext_service
'update_languages';
-- update language list
EXEC
sp_fulltext_service
'restart_all_fdhosts';
-- restart daemon
reconfigure
with override;
10)
Restart the
server
11)
select document_type,
path from
sys.fulltext_document_types
where document_type
= '.pdf'
-select
document_type,
path from sys.fulltext_document_types
where document_type
= '.docx'
12) Results are OK.
Following is my Table /Index/ catalog script:
CREATE
TABLE dbo.DocumentFilesTest
DocumentId INT
IDENTITY(1,1)
NOT NULL
PRIMARY KEY,
AddDate datetime
NOT NULL,
Name nvarchar(50)
NOT NULL,
Extension nvarchar(10)
NOT NULL,
Description nvarchar(1000)
NULL,
FileStream_Id UNIQUEIDENTIFIER
ROWGUIDCOL NOT
NULL UNIQUE DEFAULT
NEWSEQUENTIALID(),
FileSource varbinary(MAX)
FILESTREAM DEFAULT(0x)
go
--Add default add date for document
ALTER
TABLE dbo.DocumentFilesTest
ADD CONSTRAINT
DF_DocumentFilesTest_AddDate
DEFAULT sysdatetime()
FOR AddDate
EXEC
sp_fulltext_database
'enable'
GO
IF
NOT EXISTS
(SELECT
TOP 1 1 FROM sys.fulltext_catalogs
WHERE name
= 'Ducuments_Catalog_test')
BEGIN
EXEC sp_fulltext_catalog
'Ducuments_Catalog_test',
'create',
'D:\SQL\PDFBlob';
END
--EXEC sp_fulltext_catalog 'Ducuments_Catalog_test', 'drop'
DECLARE
@indexName nvarchar(255)
= (SELECT
Top 1 i.Name
from sys.indexes
i
Join sys.tables
t on
i.object_id
= t.object_id
WHERE t.Name
= 'DocumentFilesTest'
AND i.type_desc
= 'CLUSTERED')
PRINT @indexName
EXEC
sp_fulltext_table
'DocumentFilesTest',
'create',
'Ducuments_Catalog_test',
@indexName
EXEC
sp_fulltext_column
'DocumentFilesTest',
'FileSource',
'add', 0,
'Extension'
EXEC
sp_fulltext_table
'DocumentFilesTest',
'activate'
EXEC
sp_fulltext_catalog
'Ducuments_Catalog_test',
'start_full'
ALTER
FULLTEXT INDEX
ON [dbo].[DocumentFilesTest]
ENABLE
ALTER
FULLTEXT INDEX
ON [dbo].[DocumentFilesTest]
SET CHANGE_TRACKING
= AUTO
ALTER
FULLTEXT CATALOG
Ducuments_Catalog_test REBUILD
WITH ACCENT_SENSITIVITY=OFF;
INSERT
INTO DocumentFilesTest(Extension,
Name,
FileSource)
SELECT
'pdf'
'BOL12006553.pdf'
* FROM
OPENROWSET(BULK
'd:\SQL\PDFBlob\BOL12006553.pdf',
SINGLE_BLOB)
AS BLOB;
GO
INSERT
INTO DocumentFilesTest(Extension,
Name,
FileSource)
SELECT
'docx'
'test.docx'
* FROM
OPENROWSET(BULK
'd:\SQL\PDFBlob\test.docx',
SINGLE_BLOB)
AS Document;
GO
SELECT
d.*
FROM dbo.DocumentFilesTest
d WHERE
Contains(d.FileSource,
'BILL')
Returns nothing. it should come from PDF file
SELECT
d.*
FROM dbo.DocumentFilesTest
d WHERE
Contains(d.FileSource,
'TEST')
Returns from word document as follows:
2 2014-06-04 10:11:41.393 test.docx docx
NULL [BINARY Value] [Binary Value]
Any help is appreciated. Its been a long wait.
Thanks,
Vel
Vel ThavasiHello,
Did you check the fulltext log files for more details about the errors. If the filter isn’t working, there should be errors in the error log file.
The following thread is about similar issue, please refer to:
http://social.msdn.microsoft.com/forums/sqlserver/en-US/69535dbc-c7ef-402d-a347-d3d3e4860d72/sql-server-2008-64bit-fulltext-indexing-pdf-not-working-cant-find-ifilter
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support -
I get one or the other error when i install SQL server 2012 SP1 in my Lab server
I get multiple errors when i install SQL server 2012 SP1 In my lab server.
Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
Below are error codes, screen shots and also a log of the error.
1. Eror code 0X84B40000
Also dint understand any thing from this article related to the above error
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
2. Eror code 0x851A001A
Can any one plz help as i always get one or the other error.
====================================
Screen shot:
Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
2. Log file content.
=================================
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-04 21:15:35
End time: 2014-05-04 21:51:45
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: SERVER1
Machine processor count: 2
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: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Basic
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Complete
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools SDK
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Integration Services
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: ms\sql
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: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SCOM
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SCOM
INSTANCENAME: SCOM
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SCOM
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: ms\sql
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MS\Gautam, MS\SCOM Users
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
Detailed results:
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htmSorry about the error in the path, but you find the files that's the main thing.
Indeed it is a certificate problem:
2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
Anyway, this blog post,
http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
suggests the issue is a corrupted user profile, and you should try to use a different service account.
This blog also seems to have a simple solution, but I cannot vouch for that it will work:
http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
Erland Sommarskog, SQL Server MVP, [email protected] -
Errro while installing sql server 2012 express edition on Windows 8 -64 version
Hi,
Im trying to install sql server 2012 express edition on windows 8 machine(64 bit),however im getting same error every time.
The following error has occurred:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337
i've googled and checked all prerequisite which is already installed.so not finding the reason behind this error.
it would be great if any one can help on resolving this error.
Thanks in advance
Regards
RiteshHi ,
Thanks for help. here is the log summary text
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068051679
Start time: 2014-02-05 12:30:44
End time: 2014-02-05 12:36:21
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: IDEA-PC
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
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
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services
1033 Developer Edition 10.50.1600.1 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication
1033 Developer Edition 10.50.1600.1 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Developer Edition 10.50.1600.1 No
SQL Server 2008 R2
Management Tools - Basic 1033 Developer Edition
10.50.1600.1 No
SQL Server 2008 R2
Management Tools - Complete 1033 Developer Edition 10.50.1600.1
No
SQL Server 2008 R2
Client Tools Connectivity 1033 Developer Edition 10.50.1600.1
No
SQL Server 2008 R2
Client Tools Backwards Compatibility 1033 Developer Edition 10.50.1600.1 No
SQL Server 2008 R2
Client Tools SDK 1033
Developer Edition 10.50.1600.1 No
SQL Server 2008 R2
Integration Services 1033 Developer Edition
10.50.1600.1 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\b33170cf028067db5b8335d2\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
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: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, SNAC_SDK
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: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLFASHION
INSTANCENAME: SQLFASHION
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQL$SQLFASHION
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: idea-pc\lenovo
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2337
Component log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2337
Component log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\SystemConfigurationCheck_Report.htm -
I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-PC
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
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
SQL Server 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SS2012
INSTANCENAME: SS2012
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htmPlease help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
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: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
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: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm -
SQL Server 2012 DB Engine does not start (clean install with server 2012 and 2008 R2)
I'm trying to do clean installation of SQL server 2012 on Server 2012 (which is runnning as a VM on ESX server) and getting this "wait on the DB engine recovery failed" message. Initially, I though this issue was related to some permission issues
but changing the permission or service accounts didn't help. I'm not seeing any "denied" messages in the log files either. Even with Server 2008 R2 (clean built VM), the installation gives the exactly the same error messages.
My setup is purely for test purpose; so, the security is not a concern. Can someone help or give me a clue where to look?
(Summary)
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-28 17:12:12
End time: 2014-05-28 17:19:47
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-1V3VKPV5Q19
Machine processor count: 1
OS version: Future Windows Version
OS service pack:
OS region: United States
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Evaluation
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$TESTDB
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
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: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
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: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: TESTDB
INSTANCENAME: TESTDB
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$TESTDB
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-1V3VKPV5Q19\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\SystemConfigurationCheck_Report.htm
(Error Log)
2014-05-28 17:17:26.64 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2014-05-28 17:17:26.73 spid9s Starting up database 'model'.
2014-05-28 17:17:28.24 spid9s Error: 9004, Severity: 23, State: 6.
2014-05-28 17:17:28.24 spid9s An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2014-05-28 17:17:28.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
(Details)
(01) 2014-05-28 17:17:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2014-05-28 17:17:28 Slp: Message:
(01) 2014-05-28 17:17:28 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2014-05-28 17:17:28 Slp: HResult : 0x851a001a
(01) 2014-05-28 17:17:28 Slp: FacilityCode : 1306 (51a)
(01) 2014-05-28 17:17:28 Slp: ErrorCode : 26 (001a)
(01) 2014-05-28 17:17:28 Slp: Data:
(01) 2014-05-28 17:17:28 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2014-05-28 17:17:28 Slp: WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp: WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2014-05-28 17:17:28 Slp: Stack:
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2014-05-28 17:17:28 Slp: Watson Bucket 1
Original Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp:
Final Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : 0x9C5770A6Hi Nababoya:
As you are telling this is a test installation process...
In the logs i m seeing the error message "An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.".
1) If the SQL Services was installed successfully and SQL Service was not able to start because of model database issue...
1.1) If you have model database SQL back file, start the SQL Server in single user mode with minimum configuration and try to restore MODEL database
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/05/11/inf-hey-my-sql-server-service-is-not-starting-what-do-i-do.aspx
1.2) If you don't have backups., try to rebuild the system databases but make sure that you are not losing any data critical data on master and SQL Jobs on MSDB
http://msdn.microsoft.com/en-us/library/dd207003%28v=sql.110%29.aspx#RebuildProcedure
2) As if this is a new installation try to repair the instance with the help of setup media file
3) If the repair option fails., the last option wipe out the complete SQL Server components from Services.msc and Registries and start new installation.
4) Make sure when you are doing un-installation all the required SQL Server components on services.msc should be in stop state.
Hope this helps and let me know any questions...
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)
Maybe you are looking for
-
Eorror in Opening a query after Authorization
Dear Experts, in a requirement to restrict the users to access some specific queries only I have created the role and assigned some queries to those role in PFCG. The user is able to see only the authorized queries when he login to BEx Analyzer . Now
-
I bought a book and at fierst the download was not responding.it tookna while to respond and when it did there was 6 books downloading but they were the same book and i want to make sure they don't charge me for all 6 books . What can i do ?
-
Restoring iPhoto6 library to iPhoto6 on a new computer via DVD
Hello - Recently my Mac was stolen, it did have iLife 6 on it. Luckily I backed up my photo library to a DVD. I have a new iMac G5 with iLife 6 and tried to restore my Photo library. I dragged and dropped the entire file from the DVD to the iPhotos l
-
C:\Windows\system32\ntvdm.exe Error
I keep getting this message when I start iTunes and when I go to sync my iTouch C:\Windows\system32\ntvdm.exe Error. iTunes seems to be working properly. But is annoying
-
Transferring photos to the ipod nano
Hi! I've watched the ipod nano tutorial and done excactly what it said, but still the photos that i transferred won't show up on my ipod nano. Does anyone know what i should do? Thanks /Markus