Client Tools installs per SQL Server 2012
Is there a maximum allowed install of Client Tools per purchase of SQL Server 2012? I believe we have Enterprise but may have Standard. SQL Server Management Studio Express is not sufficient because of the SSIS limitations. Thanks!
matters is the license to connect to the server SO provided that the server I was connected
to had a CAL assigned to me or it was CPU licensed then all is well, as the client tools aren’t licensed themselves
http://blogs.technet.com/b/andrew/archive/2008/07/14/licensing-sql-server-client-tools.aspx
http://www.scottandscottllp.com/main/SQL_Server_Licensing_Perils.aspx
In short client tools are free as long as they connect to core components of SQL Server – the Database Engine and the Reporting, Integration and Analysis Services – which has correct licensing.
Similar Messages
-
Installation of SQL Server 2012 express on Windows 7
Hi,
When I try to install SQL Server 2012 express, I get the following error message:
This SQL Server Setup media does not Support the language of the OS, or does not have the SQL Server English-language Version Installation Files. Use the matching language-specific SQL-Server Format and System locales through the regional Settings in the
Control Panel.
I tried changing the language via the Control Panel but it didn't help.
What should I do?Hello,
Please, you need to match the following operating system settings to the language of SQL Server (US English):
(1) operating system user interface setting, (2) the operating system user locale setting and (3) the system locale setting.
https://msdn.microsoft.com/en-us/library/ee210665(v=sql.110)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Hi Matt,
Did you follow Alberto's suggestion? and it resolve your issues? -
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 install SQL Server 2012 along with BIDS & VS 2012 on Windows 7
Unable to install SQL Server 2012 along with BIDS & VS 2012 on Windows 7 professional.
I get the below error
Could not find vsjitdebugger.exe
Blogs say anti-virus is stopping but I dont have one on the system.
Note: I had used SQL 2008 on the system previously and has a refresh i have deleted all the software to speed up the system.
Now i could not install both the software.
Can I get some help regarding this?Hi Nandu,
As your description, you come across an error(vsjitdebugger.exe cannot be found). Please confirm if the error occurs during the installation of SQL Server 2012. If so, please help post SQL Server setup logs. By default, SQL Server setup log file locates
in C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
Base on my research, this error could be caused by that the previous uninstallation is improper and vsjitdebugger.exe file could be mistakenly deleted.
To troubleshoot the issue, you could start your computer into Safe Mode and fix your problem with one of the following methods. For more information, please refer to the article:
http://www.fixerrorkit.com/fix-error/fix-vsjitdebugger.exe-error.html.
1. You could execute the sfc /scannow command following steps below.
a. Press "Windows+R", type in cmd and then right click "Run as administrator"
b. Type in sfc /scannow (There's a space between sfc and /scannow) into the dialog and hit Enter key and click ok.
c. Wait until the System File Checker finishes the check.
2. You could use a Windows repair installation, also known as a Startup Repair to repair your Windows system files.
3. You could install the latest Windows updates to fix vsjitdebugger.exe error. Microsoft often releases new service packs and system patches to replace or update some DLL files of Windows system.
4. You could use third-party tool such as Automatic Error Fix Tool to fix your vsjitdebugger.exe error. However, Microsoft cannot make any representations regarding the quality, safety, or suitability of any third-party software or information found there.
In addition, if you are unable to install Visual Studio, I suggest you post your question in Visual Studio Setup and Installation forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vssetup . It is appropriate and more experts will assist you.
Regards,
Michelle Li -
Installing Sql Server 2012 Enterprise edition on Windows 7
Hello,
I have a desktop with 1 TB Hard Disk and 8GB RAM. It has Windows 7 installed. I want this to be used as staging server at my work. I installed the SQL Server 2012 Enterprise edition. While installing I used service accounts as default when prompted
which I normally do while installing on a desktop. But now I want this to be used as a server where people can access this box as they do on a sql server machine .i.e. connect to server using SSMS and get to databases on the server and also remote
desktop into this machine. So, Is it fine to install with default service accounts?
Also how can I connect to this newly installed sql server box from another desktop using SSMS?
Thank You.Hello,
Installation of SQL server 2012 Enterprise edition on Client machine(Win 7) is not supported( you can install ) .See below for Hardware and Software requirements for SQL Server 2012.You cannot claim support from Microsoft and I guess statging
is also important.
http://msdn.microsoft.com/en-us/library/ms143506.aspx
Now to your main question.To connect
Makes sure Browser service is running
Make sure you make exception in firewall for SQL Server services and incoming connections
Make sure you specify correct instance name when connecting from remote
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
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 :) -
SQL Server 2012 Express Install on Windows 7 SP1 Embedded not using virtual account?
Hi there,
I did a default installation of SQL Server 2012 Express on Windows 7 embedded Standard SP1.
When I look at the SQLSERVER service credential it is configured to run under "NETWORK SERVICE" instead of the virtual account "NT SERVICE\MSSQL$SQLEXPRESS".
This is different from SQL 2012 Express installation on a non-embedded Windows 7.
Why is this difference?
Secondly, because of this, I am unable to take a backup of databases to any folder other than the default SQL folder.Hi Chandrasekaran,
As Local Service account, the Network Service account and high privileged Local System account could be used by many services.
It becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account or other account.
In Windows7 and Windows Server 2008R2, it introduces a new type of account called a virtual account, which emulates creating many unique instances of the Network Service account, so each service runs with its own instance of the Network Service account.
For example, when you install SQL 2012 on Windows Server 2008 R2 or Windows 7 and later you’ll see the services run with virtual service accounts named like:
in the format NT SERVICE\<SERVICENAME>.
According to your description, when the SQLSERVER service was run under “NETWORK SERVICE”, you only back up database to the default SQL folder. It may be caused by the NETWORK SERVICE account has limited local privileges, just accesses network
resource with the computer credential. I recommend you change the account to Local System account, by default, which has full permissions on your computer.
For more information about SQL Server service account and virtual account, you can review the following articles.
http://www.travisgan.com/2013/06/sql-server-service-account-and-per.html
http://www.sqlservercentral.com/blogs/sqldbauk/2014/01/13/sql-server-2012-and-virtual-service-accounts/
http://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
SQL Server 2012 Install Failure
I am attempting to install SQL Server 2012 Developer Edition with SP1 as a standalone installation. This is the downloaded version. en_sql_server_2012_developer_edition_with_sp1_x64_dvd_1228540
Here is my environment. Windows 7 X64, SQL Server 2008 R2 Developer Edition,
I've tried to bypass the update step by executing as: "setup.exe /ACTION=Install /UpdateEnabled=False". While this did eliminate the two KB downloads, the same error still occurred.
I've extracted the ISO to my local machine and attempted the install according to another thread. Still no joy.
I installed a hotfix recommended by another thread but still no joy. System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2013]
The Error occurrs in pop-up during Product Updates.
2 updates found
SQL Server 2012 SP1 GDR Product Update 145MB KB2793634
SQL Server 2012 SP1 GDR Setup Update 26MB KB2793634
ERRORS
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32-policy"'. Please refer to Help
and Support for more information. HRESULT: 0x800736B3.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xDF039760%25401201%25401
BUTTONS:
OK
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
SQL Server Setup has encountered an error when running a Windows Installer file.
Windows Installer error message: An error occurred during the installation of assembly 'policy.8.0.Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32-policy"'.
Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Windows Installer file: C:\Users\jhadden\AppData\Local\Temp\SQL Server 2012\Setup\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi
Windows Installer log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131010_091212\SqlSupport_Cpu64_1_ComponentUpdate.log
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xDC80C325
BUTTONS:
&Retry
CancelHello,
Did you install Windows 7 update SP1? If not, please install the SP1 update first.
What's more, you try to install SQL Server 2012 SP1 together with SP1 Cumulative update (KB2793634)by enable the "UpdateEnabled" and specify the update feature in "UPDATESOURCE".
You can refer to Ahmed's blog for more details steps:
http://blogs.msdn.com/b/ai/archive/2013/01/14/installing-sql-server-2012-service-pack-1-sp1-cumulative-update-in-one-installation-using-sql-server-2012-product-update.aspx
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
SQL Server 2012 - Cannot connect to SQL Alias (Connection to serverName is good)
Hi there,
On my 64 bit installation of SQL Server 2012 - I have enabled SQL Alias using cliconfg 32 bit and as well as on cliconfg 64 bit.
On my WFE (Web Front End server) I have set the SQL ALias as well (both 32 bit and 64 bit).
From WFE (Web Front End) server I can ping the SQL server name but cannot ping the SQL ALias. Any clue what I might be missing?
Thanks.but cannot ping the SQL ALias
Hello,
Of course you can't "ping" a SQL Server alias, this Setting is only used by SQL Server Client components and not by any other network component. You could use
SqlCmd or SSMS or ODBC admin to test the alias.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
Licensing SQL Server 2012 Management Studio
Hi all,
I've an installation of SQL Server 2012 Standard Edition licensed under "per core" model.
May I install Sql Server Management Studio on the workstations of the dba? (let's say 5 workstation)
Am I violating any license?For question regarding pricing / licensing please contact a Microsoft sales partner or licensing expert.
Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist. -
Microsoft SQL server 2012 express
i recently downloaded ENU\x86\SQLEXPR_x86_ENU.exe and ENU\x86\SQLManagementStudio_x86_ENU.exe from microsoft SQL server 2012 from official download centre page. First i installed SQLEXPR_x86 (database engine) with mixed mode authentication, then i installed
management studio with new installation option rather than selecting add new features.after both the successfull installation i learnt that in the object explorer, expanding database+system database+master i dont have a table option to create
new tables as earlier found in sql 2005 and 2008 versions. in simple words i dont have a table designer to create table, i have to type the statments using query editor to create and do manipulations in the table. for your further help i want to
tell you some related information:
1.i tried to get the table option with ENU\x86\SQLEXPRADV_x86_ENU.exe and ENU\x86\SQLEXPRWT_x86_ENU.exe without installing management studio as studio is already present in these packages. but still the problem persist.
2.i have windows 7 home basic installed on PC and windows 7 home premium on laptop both with service pack 1 with all the new updates.
3.after installation of sql server 2012 service pack, i thought problem might get solved but no.
i really need table designer feature.Hello,
It is simple : in SSMS , after having connected to your SQL Server instance, you should see in the left panel a TreeView with the name of your instance. Right-click on the name of your instance .I n the context menu , click on Facets ( 12th item just above
Start PowerShell ).You will open a new form labeled "View Facets" followed by the "full" name of your SQL Server. In the bottom left part , you should see view the connection string .Click on it.
If the name of your database is master , it means that you are connected to the master database . The master database is a system database in which you are not allowed to create a new table ( it is an essential database containing information essential to
the survival of your SQL Server ).See this link ( even if it was for SQL Server 2012, it is always valuable )
http://www.mssqltips.com/sqlservertip/1420/sql-server-system-databases/
I would suggest to have a look at this link :
http://msdn.microsoft.com/en-us/library/ms187837.aspx ( special 2012 ) and especially the part recommendations.
As you have not yet created an user database , you connect automatically to the master database which is at least dangerous when you want to create a new table.
You have before to create a new database in which you will create your new table. It is what I have explained in my former post.
If you don't know how to create a new database, you have not posted in the good forum ( a curious habit from the original posters , maybe because they don't understand how to find the "good" forum but I recognize that I am often hesitating before finding
the most appropriate forum even if I am moderator since 6 years ). It is possible that I have not been clear enough but English is not my mother tongue ).
So don't hesitate to post again to obtain more help and explanations : this forum is full of highly-qualified persons always ready to help persons lost in SQL Server.
For me , you have 2 important steps :
- create a new database
http://msdn.microsoft.com/en-us/library/ms176061(v=sql.120).aspx
http://msdn.microsoft.com/en-us/library/ms186312(v=sql.120).aspx
- create a new table
http://msdn.microsoft.com/en-us/library/ms174979.aspx
According to me , it is simpler to create a new database or/and table without using TRANSACT-SQL through the visual interface of SSMS
for a database : right-click on the Databases node of your SQL Server instance and click on Create Database
for a table : as soon as you have created your database , its name should appear in the list under the Databases node.
Click on the little + on the left of this name to expand the node related to this new database.
Right-click on the Tables node and choose New Table. You should arrive to a new form making relatively easy the creation of the table , more exactly , the structure of the table with its columns ( names and data types ).
Don't hesitate to post again if you need more help( it is what I am doing when I am lost ) : you will find always someone available to help you at any time as moderators/answerers are nearly from every continent at any hour of the day ( when USA is sleeping
, Europe and Asia are awake ... )
Have a nice day
Mark Post as helpful if it provides any help.Otherwise,leave it as it is. -
Access 2007 ADP to SQL Server 2012 with extended protection
Hello,
I have a Access 2007 ADP client connecting to an sql server 2012. This works fine with standard security configuration, but when I activate extended protection on the SQL server, the Access client cannot connect to the server. I am using integrated security
with a domain user and get the error message
"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication."
In sql server logfile I find:
"SSPI handshake failed with error code 0x80090346, state 46 while establishing a connection with integrated security; the connection has been closed. Reason: The Channel Bindings from this client are missing or do not match the established Transport
Layer Security (TLS) Channel".
Is there any "easy" solution other than developing a new client based on an up to date Office version or Dot.Net?
Regards,
charles-fWell, I have no problem connecting to the sql server from my pc using ssms with my domain account. I have also sucessfully create a odbc connection using the "SQL Server Native Client 11.0" driver and my domain account. My account is in a trusted
domain, so this seems not to be the problem.
To me it rather looks like if Access is using an old driver which does not support the tls encryption required by the extended protection settings.
regards, charles-f -
Installation of SQL Server 2008 failing - Client Tools
Hello,
I am trying to install SQL Server 2008 Client Tools on a machine that already has SQL Server 2005 (Full install). I select "Client Tools Connectivity" "Client Tools Backwards Compatibility" "Client Tools SDK" and "SQL Client Connectivity SDK". During installation, I receive this error message "A network error occurred while attempting to read from the file E:\x86\setup\x86\sqlncli.msi". The installation then fails. Is the older version of sql native client interfering with the new install? Any suggestions on what to do? Thanks!!
-TheresaSo I tried to reinstall missing features, but I was getting the same error message about the sqlncli.msi file. I tried executing it from the folder, but got the same error.
When I went to remove the items that did get installed from Add or Remove Programs, I got the following error:
"SQL Server Setup has encountered the following error:
No feature were uninstalled during the setup execution. The requested features may not be installed. Please review the summary.txt log for further details.
Error code 0x84B30002"
Not sure what to do.. -
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 -
Connect SQL Server 2012 from Windows Server 2003 with native client 9.0
Hi,
I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
Now I have the requirement to upgrade the SQL server from 2005 to 2012.
My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
Thanking you in advance!Hi Soumya,
Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
Regards,
Mike Yin
TechNet Community Support
Maybe you are looking for
-
How to retrieve data from the Database after deleting rows from VO ?
Hello, I am using Jdeveloper 11.1.2.1.0 I have a master and a child . So according my use case when a value in the master vo changes the corresponding child has to be deleted. but when i change back to any other value i want to undo the delete operat
-
Java interface as an Axis Web Service
Hi averybody: I'm developping an application containning a web service using Axis 1.2 with Tomcat 5.5.7. I had design a Java interface for the WS and create mi deploy.wsdd file for it using Message-style. Everithing goes right in deployment process,
-
Adobe Form unable to Save work
Hi All, I'm creating a Adobe Form via NWDS. under the View -> Layout -> InteractiveForms-> Edit(right click), I've created some input fields and display fields. Then save all MetaData, Rebuild project. After that when I'm trying to edit the Form agai
-
If a column is renamed that will impacts for 100 reports?
Hi Gurus, I have a column called Emp Name and that column is used for 100 reports, now the client is asking like he wants Employee Name instead of Emp Name and in future also Employee Name is fixed. So what we need to do I should I rename all the 100
-
Have a MF8580Cdw that will not copy
Have a MF8580Cdw that will not copy. The little lights on the B&W and color start buttons are no longer lit up either.