"Add components to your existing installation" disabled in SQL Server 2000 clustered installation.
When I try to add the
fulltext service to a named instance in
SQLServer 2000, I see the option "Add components to your existing installation"
in gray.
I launched
the installer both ways, with the services stoped and started,
and always the same result.
Please check the below link and try..
http://technet.microsoft.com/en-us/library/aa197936%28v=sql.80%29.aspx
http://www.databasejournal.com/features/mssql/article.php/3441981/Full-Text-Search-on-SQL-2000-Part-1.htm
Raju Rasagounder Sr MSSQL DBA
Similar Messages
-
Problem with NW04s SR2 installation with MS SQL Server 2000 SP4
Im struggling with the NW04s installation with MS SQL Server 2000.
The installation stops at the step Create/modify database schema SAPJ2EDB.
The following error/info from log file,
INFO 2007-06-06 12:02:33 [iaxxgenimp.cpp:632]
showDialog()
Execute step doConfiguration of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|NW_MSS_SRVCFG|ind|ind|ind|ind|6|0.
INFO 2007-06-06 12:02:35 [iaxxgenimp.cpp:632]
showDialog()
Execute step doTempdb of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
showDialog()
Execute step doSwitch of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
showDialog()
Execute step doTempDBAnalyze of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:02:37 [iaxxgenimp.cpp:632]
showDialog()
Execute step doTempDBBeforeRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:02:38 [iaxxgenimp.cpp:632]
showDialog()
Execute step doRestartServer of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:02:58 [ianxbservi.cpp:697]
CIaNtServices::stop(const map<iastring,iastring>&)
The service 'MSSQLSERVER' stopped successfully on host 'GBCZ672C'.
INFO 2007-06-06 12:03:10 [ianxbservi.cpp:632]
CIaNtServices::start(const map<iastring,iastring>&)
The service 'MSSQLSERVER' started successfully on host 'GBCZ672C'.
INFO 2007-06-06 12:03:21 [ianxbservi.cpp:632]
CIaNtServices::start(const map<iastring,iastring>&)
The service 'SQLSERVERAGENT' started successfully on host 'GBCZ672C'.
INFO 2007-06-06 12:03:21 [iaxxgenimp.cpp:632]
showDialog()
Execute step doTempDBAfterRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:03:22 [iaxxgenimp.cpp:632]
showDialog()
Execute step doChangeTempSetNewSize of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO 2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
showDialog()
Execute step CheckParameters of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
INFO 2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
showDialog()
Execute step CreateDirectories of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
INFO 2007-06-06 12:03:40 [iaxxgenimp.cpp:632]
showDialog()
Execute step CreateDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
ERROR 2007-06-06 12:03:40 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
ERROR 2007-06-06 12:03:40
lib=iamodmssql module=CIaNtMssDmo
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
INFO 2007-06-06 12:04:04 [iaxxgenimp.cpp:774]
showDialog()
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase".
ERROR 2007-06-06 12:04:05 [iaxxgenimp.cpp:731]
showDialog()
FCO-00011 The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
Please let me know if you can help or if there is any other way around.
Many Thanks in advance.
Ritin JainHi All,
I was not able to solve the problem with MS SQL 2000, but I was able to resolve the issue with MS SQL 2005.
You have to chhose the following settings while instalation,
Service Account - Select one of the following options:
1) Use the built-in System account for each service and choose Local system or Network Service.
2) Use a domain user account, and enter the user name and password.
Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected.
Authentication Mode
1) Select Mixed Mode (Windows Authentication and SQL Server Authentication).
This mode is required for a Java or ABAP+Java system.
If you choose this mode, you have to set the password for the sa login.
Note: The password for the sa login must comply with the Windows password policy.
Collation Settings
1) Select SQL collations (used for compatibility with previous versions of SQL Server).
2) From the drop-down list select Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set.
I hope this helps! -
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 -
Service accounts rights in Sql Server 2008 clustered installation.
I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.
You should get Domain account created before starting cluster installation and specifically give these rights to the account.
Regarding rights below link might be helpful
http://blogs.msdn.com/b/askjay/archive/2011/02/28/required-rights-for-sql-server-service-account.aspx
When installing cluster make sure you use Domain account which is added as local administrator on both nodes.
It should have righst to create Computer name object(CNO) in domain where cluster is being created
Windows CNO must have complete rights on SQL server CNO.You should also take help from AD team in providing these rights and understanding if any.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
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 -
Installing Java Add-In for an existing ABAP System -Error SQL compatibility
Hello gurus,
We have a system and it has only the ABAP instance! So my goal is install the JAVA iinstance. In this momment I´m reading the section "4.4.2 Installing the Java Add-In for an Existing ABAP System (Optional)" in installation guide "SAP ERP 6.0 SR3" (ABAP+JAVA). So, I want to install the JAVA instance which is the Java Add-In for an existing ABAP system!
So what I did was followed that instructions on that section in guide!
As you certainly know this process has three sequential phases:
1) Central Services Instance (SCS) Java Add-In
2) Database Instance Java Add-In
3) Central Instance Java Add-In
The first phase - Central Services Instance (SCS) Java Add-In - it already finished with success, but I´m faccing with a weird error in second phase Database Instance Java Add-In when I entered all required input parameters, SAPinst shows an error that says:
The database PRD has the wrong compatibility level. The database used for the installation of an SAP system must have compatibility level: 80 for MS SQL Server 2000 90 for MS SQL Server 2005 SOLUTION: See the MS SQL Server documentation on how to set the compatibility level for a database.
I don´t know what´s happen, in fact my database is an SQL Server 2008 (100), but I already change it at management studio, the compatibility level to MS SQL Server 2005, but still the error remains!!! I also tried to ran again the sapinst process, I restarted it but it still show me this error!!
Can you tell me why and how can I solve this problem?
Best regards,
João Dimas - PortugalHello Sunny,
I still have this error... I don´t know what do to more for this situation!
I found one not which report this error of compatibility - Note 1152240 - Setting Up Microsoft SQL Server 2008 (R2) - in chapter "VII TROUBLESHOOTING" which said to follow the instructions in chapter III - "Installing SAP systems based on SAP NetWeaver 7.0 SR3".
When I read this last chapter (III) it tell us to do:
If you want to install an SAP system based on SAP NetWeaver 7.0 SR3 on SQL Server 2008, you cannot use the Installation Master and Kernel DVD that you received from SAP or downloaded from SAP Service Marketplace. Instead, you have to do the following:
Patch your runtime libraries by applying the procedure that is described in note 684106 for your release and machine architecture.
Use a modified Installation Master DVD
For more information, see section "VI PROCEDURES" -> "Creating a modified Installation Master DVD".
Use a modified Kernel DVD
For more information, see section "VI PROCEDURES" -> "Creating a modified Kernel DVD".
I did everything that is said in the note (except the "Creating a modified Kernel DVD") because I can not access to the note 1480785 (it say: "The requested SAP Note is either in reworking or is released internally only")
Can you help me... can you guide me... please!?
Best regards,
João Dimas - Portugal -
SQL Server 2014 Express Installation Failure
Hi,
Now trying to install SQL Server 2014 Express on my work machine. Here is the error log. Any ideas? The error help link is useless.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-06-19 16:24:17
End time: 2014-06-19 16:38:03
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: PC12345
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 Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Scott\Software\SQLEXPRADV_x64_ENU\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, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: C:\SQL Server Data
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: INTERNAL\sbass
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140619_162416\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
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=12.0.2000.8&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=12.0.2000.8&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=12.0.2000.8&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=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140619_162416\SystemConfigurationCheck_Report.htmThanks Shanky, that fixed my issue. I reinstalled, specifying NT AUTHORITY\LOCALSYSTEM for the SQL Server Database Engine account. After the successful installation, I used Sql Server Configuration Manager to change the account to LocalService
(NT AUTHORITY\LocalService). The Database Engine is restarting OK.
So, my accounts are:
SQL Server (MSSQLSERVER): NT AUTHORITY\LocalService
SQL Full-text Fiter Daemon Launcher (MSSQLSERVER): NT Service\MSSQLFDLauncher
SQL Server Reporting Services (MSSQLSERVER): NT Service\ReportServer
SQL Server Browser: NT AUTHORITY\LOCALSERVICE
SQL Server Agent (MSSQLSERVER): NT AUTHORITY\NETWORKSERVICE
I check out the link http://msdn.microsoft.com/en-us/library/ms143504.aspx#Serv_Perm. I'm a bit confused how the NT Service\* accounts are created, such as NT Service\MSSQLSERVER. However, I did see this http://msdn.microsoft.com/en-us/library/ms191153.aspx#manual;
perhaps I need to read it further.
Regardless, this is my desktop machine, the installation is for development only, it's inside our network, and no external users will be accessing this SQL Server instance. So, while I haven't fully read the details on running under LocalService, I
believe this will meet my needs.
Thanks again for your help. -
SQL Server 2008 R2 Installation Media Root Directory location for XP SP3?
Where is the SQL Server 2008 R2 Installation Media director? This question asks during a 'new installation or add features to an existing installation'. The installation media root directory is not indicated under 'options'. I trying side-by-side
installation next to SQL Server 2008 Express Edition.
It appears that C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 (where 1033_ENU_LP, Resources, and x86 dirs are installed) is the installation media root directory, but is is not a valid folder.
Also tried copying the 1033_ENU_LP, Resources, and x86 dirs from the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 into a directory that I created in c:\2008R2installationDir, and then running setup.exe, but still do not have
an installation media root dir specified under options.There is no DVD; SQLServer2008R2SP2-KB2630458-x86-ENU.exe was downloaded. This problem occurs when setup.exe is run, after running *ENU.exe to download the files. Specifying the directory where the
SQLServer2008R2SP2-KB2630458-x86-ENU.exe doesn't help.
>>It doesn't seem like any instances have been installed, yet. Nothing shows up under Administrative Toos | Services. Under Start | Microsoft SQL Server 2008 R2 , there are two choices: Configuration Tools and Documentation&Tutorials.
Hello,
What seems to me that you have downloaded SP2 for SQL server 2008 R2(SQLServer2008R2SP2-KB2630458-x86-ENU.exe ).And as you say you dont find any thing under SQL 2008 r2.So i guess that is why SP2 installation is not moving
ahead.Can you download SQL server 208 R2 setup again and install database engine and ither fetures with client tools.And then you can move ahead with SP2 installation
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
MS SQL Server jdbc Driver installation on XI
Hi,
I am running XI 3 on sp11 patch 1.
We need to install the MS SQL Server jdbc driver on the XI box to connect to a SQL Server 2000 SP3 Database server.
We tried installing the driver from the MS downloads website:
http://www.microsoft.com/downloads/details.aspx?familyid=07287b11-0502-461a-b138-2aa54bfdc03a&displaylang=en
But this is giving us problems while installation as SDM does not like the format.
Can someone please tell us how do we install this driver?
Thanks
AshishHi Ashish,
i assume that u already have the drivers (msbase.jar,mssqlserver.jar,msutil.jar). All u have to do is deploy them.
The procedure is:
1.Add all jars to the archive <b>aii_af_jmsproviderlib.sda</b>, modify the <b>provider.xml</b> file and WinZip the .sda file again.
a)Copy the file: aii_af_jmsproviderlib.sda from the path ..\usr\sap\SID\DVEBMGS00\SDM\root\origin\sap.com\com.sap.aii.af.jmsproviderlib\SAP AG\3.0.20040112154003.0000. to any other drive on the server.
b)Unzip it. After Unzipping the archive there are 2 folders created under the provided directory
\META-INF
\server
c) Edit the file provider.xml
Add the vendor specific jar file names to the provider.xml file in between the tags <jars> </jars> and Save it.
For you it will be
<jars>
<jar-name>msbase.jar</jar-name>
<jar-name>mssqlserver.jar</jar-name>
<jar-name>msutil.jar</jar-name>
</jars>
d)Copy the specific driver files to the same dirctory where u have unzipped the .sda
e)Now ZIP the following files/folders from the drive/dirctory.
Vendor driver files
META-INF folder
Server folder
The name of the zip file should be the same i.e aii_af_jmsproviderlib.sda
2.Deploy the archive aii_af_jmsproviderlib.sda on to the J2ee Engine using SDM tool.
This will solve ur problem.
Regards
Sunita -
Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
Bypass Traverse Checking = SeChangeNotify
Lock Pages In Memory = SeLockMemory
Log on as a Batch Job = SeBatchLogonRight
Log on as a Service = SeServiceLogonRight
Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help.. -
How to find existing DAC connection to sql server
How to find existing DAC connection in sql server
Hi RoyalM,
Vishal has answered your initial question. If you have the connection issue. I suggest you elaborate the issue in a new thread.
You can access DAC using SQLCMD from a command prompt. Or check the existing DAC connection in a command prompt:
1. Open Command Prompt.
2. Type: SQLCMD –S <servername\instance> -d master and press Enter.
1> SELECT name,local_tcp_port FROM sys.dm_exec_connections ec join sys.endpoints e on (ec.endpoint_id=e.endpoint_id) WHERE e.name='Dedicated Admin Connection'
2> go
3. If it returns the result, it means there is an existing DAC connection. It also shows the port used by dedicated admin connection.
Thanks.
Tracy Cai
TechNet Community Support -
Regarding ReCreating Catalog in SQL Server 2005 which was existing in SQL Server 2000
Hello
I was using SQL SERVER 2000 ... In one table I've created FULL TEXT SEARCHING ( Full text catalog along with full text indexing)
Now we had to install our db in SQL SERVER 2005 standard edition. But while taking script it gave me two lines like:
if (select DATABASEPROPERTY(DB_NAME(), N'IsFullTextEnabled')) <> 1
exec sp_fulltext_database N'enable'
GO
if not exists (select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog')
exec sp_fulltext_catalog N'DEV_CAS_DiagnosisCatalog', N'create'
GO
so I used this in the new db creation script...
But I couldn't get where it actually is in SQL SERVER 2005 standard edition.
and also plz help how should we create if it doesn't exist...
What could be the problem....
Thanks In advanceif (select DATABASEPROPERTY(DB_NAME(), N'IsFullTextEnabled')) <> 1
exec sp_fulltext_database N'enable'
GO
if not exists (select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog')
exec sp_fulltext_catalog N'DEV_CAS_DiagnosisCatalog', N'create'
GO
sp_fulltext_catalog [ @ftcat= ] 'fulltext_catalog_name' ,
[ @action= ] 'action'
[ , [ @path= ] 'root_directory' ]
Full-text catalog and index data is stored in files created in a full-text catalog directory(not on SSMS). The full-text catalog directory is created as a sub-directory of the directory specified in
@path or in the server default full-text catalog directory if
@path is not specified. The name of the full-text catalog directory is built in a way that guarantees it will be unique on the server. Therefore, all full-text catalog directories on a server can share the same path.
Refer the path column by running the below query. full text catalog file is created under the root directory by default if the path is not specified.
select * from dbo.sysfulltextcatalogs where name = N'DEV_CAS_DiagnosisCatalog'
Refer
http://technet.microsoft.com/en-us/library/ms189520(v=sql.90).aspx
Regards, RSingh -
ERP ECC 6.0 Cluster Installation under MS SQL Server 2005
Hi,
anybody in the world did a ECC 6.0 Cluster installation under MS SQL Server 2005 database?
Can anyone please share some usefull documents to understand... This is new to me and doing it for first time.
Pls help
RGCHi,
I'm looking for a customized document for ECC installation (how to document) and not a SAP Standard one as i'm new to cluster. Please share if any.
How to configure the nodes in three tier architecture?
In which node the DB should be installed?
In which node the CI should be installed?
How to configure Central Point of Failure (CPOF)?
How the ECC 6.0 cluster works and how to distribute the resources (SAP) across nodes?
What are the resources that needed for failover from one node to another?
Expecting help.
rgds
RGC -
Error during installation of Microsoft SQL Server 2005
Hello All,
During installation of Microsoft SQL Server 2005 I have got the below error message
"There was an unexpected failure during the setup wizard"
From this link http://support.microsoft.com/kb/916760 i came to know that this error occurs just because I used SQL Server 2005 installations from a folder on a network share.
After that i unstall everything & copy the installations in a local drive. But again when we restart the activity we got the same error message & the installation completed.
Any hint why this happens..
Thank You.
Kind Regards,
JitudaHello Jituda,
I think we need to focus on the error in the setup log first.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
you might be able to see more detailed error information in the log.
You may check if the following links help:
http://www.sqlserverfaq.net/2008/12/17/sql-server-2005-setup-failing-to-install-on-cluster-with-unexpected-failure-while-performing-the-scc-checks/
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f998b073-4378-4d02-95ac-c9afb31c7a60
In addition, to clarify, the SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the
script in an MSCS configuration, you get an error message. In MSCS configuration need to install the SQL Server database software manually instead of using the script. Please see the corresponding SAP product installation guide under http://service.sap.com/instguides
Kind regards,
Qingqing Wang -
MySAP ERP 2004 Installation with MS SQL server database
Hi all,
I m trying to perform the DB instance of mySAP ERP 2004 on a MS SQL Server, but during the process of SAPSSEXEC
the my MS SQL server stops and I the SAPSSEXEC.log files ends up with a fatal error:DB connection failed.
I stoped and restart the installation but the same error repeats. Can anybody try to help me out in this regard.
Thanks
YogiHi Yogi
I am facing the same problem as you:
I have been installing ECC5 SR1. The Centrale Instance installation happened very well.
The problem is with The Database installation. At the phase 16 of 29, Database load, the R3load jobs take more than 21 hours and often finish with the following sql error message in the log files:
<i>(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX [DD03L~1] ON [DD03L] ( [TABNAME] , [AS4LOCAL] , [POSITION] , [AS4VERS] ) )
DbSlExecute: rc = 99
(SQL error 21)</i>
I am working on :
- Windows 2003 server
- The DB is on
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
I come all the way to read that you have solved the same problem. Can you help me please.
Thanks.
Belehego
Maybe you are looking for
-
Problem with CheckBox as table cell renderer
i m making a JTable having three columns. i m also making a cellRenderer of my own MyRenderer extending Jcheckbox and implementing TableCellRenderer now i m setting MyRenderer as renderer for third column in my table and DefaultCellEditor with jcheck
-
Urgent, Help on conversion: xml to flat file
Dear experts, Here is the scenario, XML FILE ->XI-> JMS In JMS recevier side, we use localejbs/AF_Modules/MessageTransformBean to convert xml to flat file. Transform.Class: com.sap.aii.messaging.adapter.Conversion Transform.ContentType: text/plain;ch
-
Stop rolling the the paper out in dot matrix priner once the print is done
Hi, I have used the below code to print a document and the printer used is dot matrix But,it rolls out the page once the print is done. I want to control the printer so that it stops rolling out the page once the print is done. Or set the print based
-
Can we limit the file type in Attachment?
Hi, Is it possible to limit the file types that the OAF attachment can upload? Thanks! Edited by: maeve on Apr 17, 2011 7:09 PM
-
Hi Frendz, I got struck with the product details change when i navigate through IC WC. Does CRM have BAdi link with IC WC to change product details at run time. tks, Macs.