Hi. I am DBA of SQL Server 2014 Enterprise SP2 on Windows server 2012 R2.

I just got alert from vulnerability scan that it is required to patch KB4505217 to my SQL server. I run the below query to my SQL server, I confirm service pack is SP2-CU11 and build version is 12.0.5579.0 there.

Select @@version
----------------------------
Microsoft SQL Server 2014 (SP2-CU11) (KB4077063) - 12.0.5579.0 (X64)   Feb 21 2018 12:19:47   Copyright (c) Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor) 

In my research, the required patch KB4505217 have two kind of patch for SP2.

(1) Description of the security update for SQL Server 2014 SP2 GDR: July 9, 2019

(2) Description of the security update for SQL Server 2014 SP2 CU17 GDR: July 9, 2019

The (1) is patch for build version 12.0.5223.6

The (2) is patch for build version 12.0.5659.1

My SQL server is build version 12.0.5579.0

In this case, Which patch should I apply? Or Should I upgrade my SQL server to required build version at first, then I should patch it? If so how I can find the patch to upgrade build version to required version? (My DB server is located in internal network that is not allowed to access to internet, so I need to download a patch for standalone manually)

Any advices will be gratefully appreciated it. Thank you. 

Hi,

I had already installed sql server 2017 in my machine and one of my application installed SQL server 2008R2 express edition on my machine to run itself. After installed application isn't worked properly as it couldn't connect the server because sql server instance is in stopped state. And I couldn't start the service.

Note: If I install that same application on the machine, where sql server 2016 was installed, it is working fine.

Thanks

I would like to try to install SQL server and PostgreSQl on a linux system. It is a test environment.

This is just for explore and learn Linux and how to work with database.

What Linux system do you recommend,

Redhat or Ubuntu?

Thanks

SQLFriend

Hello Everyone:

Actually i have a windows server 2012 R2 standard and isntalled SQL Server 2012 Standard SP3.  In Windows Update appeared a new patch (KB4057115).  When we tried to install this patch, appeared the following error 

I don't know why the message shows that we have isntalled is 11.1 and the version expected is 11.3.  We check the version in instance and we see that version is 11.0.6020

So, my questions are:

1) What Do i need to do in this case for applying this patch?

2) Is correct that i need install this patch?

3) Why version in my case is 11.0.6020 and it is Service Pack 3?.  I checked on internet and i just can identify that version SP3 is 11.0.6020 and not 11.3.6020.  Do exists any difference about two versions or Are they the same?

Please help me with this weird case.

Kind Regards

Hi,

I have very specific problem. I was using SQL server 2014 to some project. Project of, all data gone. Now I trying uninstall SQL Server because I don't need it. But i get every time on every package the same error. Can somebody help me uninstall it and debug problem?

 I was try uninstall it via control panel and via powershell. It not help

I got error in popup:

"The folder path "Microsoft SQL Server" contains an invalid character."

Hi,

I'm having an issue when starting my mssql-server.service on Linux.

The following error message is generated:

sqlservr: Unable to read instance id from /var/opt/mssql/.system/instance_id: Success (0)
This program has encountered a fatal error and cannot continue running at Wed May 15 12:24:22 2019
The following diagnostic information is available:

Reason: 0x00000003
Message: Unexpected call to legacy ABI.
Stacktrace: 000055c1f94c6464 000055c1f94c5fdf 000055c1f940a66e
               000055c1f9457977
Process: 23721 - sqlservr
Thread: 23722
Instance Id:
Crash Id:
Build stamp: 70437f6583b8ef39b1ef70539ef84690980315dc7a4436c9c40015f28610e4aa
Distribution: Ubuntu 16.04.6 LTS
Processors: 4
Total Memory: 12598861824 bytes
Timestamp: Wed May 15 12:24:22 2019
Aborted (core dumped)

Does anybody know what is wrong, and why i get this error message?

Any help is appreciated

Hi,

I have SQL Server 2014 SP2. I need to apply SP3, CUs & Security patches to it. What should be the sequence? Is the below correct sequence: 1) Apply SP3, 2) Apply CU3 3) Apply 4505422 Security Update for SQL Server 2014 SP3 CU3 GDR:July 9,2019 CVE-2019-1068. 

I am DBA of SQL Server 2014 Enterprise SP2. SQL server is installed on Windows Server 2012 R2 Standard that is virtual server.

I got this warning message as below during 'Check File in Use' process when I manually patch kb4505419 to upgrade my SQL server from SP2-CU11 to SP2-CU17.

I forcedly stop two process WMI Provider Host from task manager as below, then I could go on patching process.

My concern is what is the cause of the warning message. What can I do not to show this message up from next time?

I also would like to know if I do patching for SQL server, should I stop the all SQL server services before patching?

Any advice will be appreciated.  

We are doing an in-place upgrade of SQL Server 2016 with SSIS & SSAS to SQL Server 2017.

Microsoft documentation shows the process. SQL Server part pretty straight forward but I got few questions about SSIS & SSAS as I don't know much knowledge about these Services.

SSIS

After upgrade, I will end up with 2 versions of SSIS Services (SSIS 13.0 and SSIS 14.0). Do I need to stop and disable the SSIS 13.0 ? or it needs to be remain place until the developers have upgraded the existing SSIS packages from 2016 to 2017 ?

The documentation says the packages will automatically get upgraded at run time (temporary) every time they are run. Does the SSIS packages automatically run under SSIS 14.0 after upgrade or I need to change something (like SSISDB compatibility or update package individually somewhere) before they can run and until then they will continue to run in SSIS 13.0 compatibility mode.

When can the SSIS 13.0 service stopped/disabled ?

Can it be removed (and how its uninstalled) or it shouldn't be removed ?

SSAS

Is there anything I need to do explicitly post upgrade from Administration/configuration level for SSAS?

Hello:

We redistribute SQL Server express 2008 R2 core engine and deploy it automatically without user intervention on customer’s machines. This has worked out fine for us so far.

Now we will be using the full text indexing part which only comes with the Advanced Services install. Our issue is that this download is about 800 MB (x64) which is obviously not viable for redistribution. So we tried to just use the sql_fulltext.msi directly and see if we can install the full text search service that way over the core install. Initially it complained about passing the instance ID which we did but now the msi installer just vanishes after extracting the contents. I have searched high and low to find the exact parameters to pass to this msi but came up dry. So help with the following will be greatly appreciated:

1.  Is it possible to use the sql_fulltext.msi to directly install the indexing service over a core installation? Where can we find the parameters doc for this?
   
   
2.  If the above is not possible is there a way to include just the full text search in the core installation? 

I have a feeling that this should somehow be possible as this is the express edition – meant for smaller installations and redistribution by ISVs.

Distributing 800 MB file with our installer or having our non-techy customers to download and install the necessary services would not be a viable option. 

Thank you in advance for your time and insights on this matter.

KP

One of our admins accidentally deleted it from Windows Server's Programs and Features menu. I can't seem to find it listed anywhere when I rerun setup. I installed Client Tools from the installation menu but that has not restored it.

Any help would be much appreciated.

Almost no one used raw partitions on Win for SQL storage as it was discouraged by MS, but is Linux different?  Is it even possible in SQL on Linux?

FYI: SQL supported (supports??) raw partitions on Windows for storage, who knew ¯\_(ツ)_/¯

Hi,

I got a 2-node sql server 2008 R2 failover cluster (64 bit) to patch SP2. One of the node failed with error during sp2 installation as below. Please check and help.

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
  Start time:                    2013-03-07 20:09:53
  End time:                      2013-03-07 20:19:46
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                  The directory 'f:\275f14ca3bc4000435db3d388419a854\' doesn't exist.
  Start time:                    2013-03-07 20:16:40
  End time:                      2013-03-07 20:18:48
  Requested action:              Patch

Detail:

2013-03-07 20:16:00 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:16:00 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:16:00 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:16:00 Slp: Sco: Returning service status Running
2013-03-07 20:16:00 Slp: The following NT service was in a running state prior to patch action: ReportServer
2013-03-07 20:16:00 Slp: Attempting to run patch request for instance: MSSQLSERVER
2013-03-07 20:18:48 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2068709375)
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLBrowser
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLBrowser
2013-03-07 20:18:48 Slp: Sco: Service SQLBrowser started
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Sco: Attempting to get service start mode for service SQLWriter
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:48 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:48 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:48 Slp: Restoring the following NT service to a running state after patch action: SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter, start parameters
2013-03-07 20:18:48 Slp: Sco: Attempting to start service SQLWriter
2013-03-07 20:18:49 Slp: Sco: Service SQLWriter started
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Sco: Attempting to get service start mode for service ReportServer
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API for buffer size
2013-03-07 20:18:49 Slp: Invoking QueryServiceConfig Win32 API with AllocHGlobal buffer
2013-03-07 20:18:49 Slp: Sco: Returning service start mode Automatic
2013-03-07 20:18:49 Slp: Restoring the following NT service to a running state after patch action: ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer, start parameters
2013-03-07 20:18:49 Slp: Sco: Attempting to start service ReportServer
2013-03-07 20:18:59 Slp: Sco: Service ReportServer started
2013-03-07 20:18:59 Slp: Completed Action: RunPatchAllInstanceAction, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidatePatchInstanceName due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ExecutePatchCalculateWorkflow due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalCalculateSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidateFeatureSettings due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: AddPackageInstallerEnginesAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: SchedulePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleUpgradePackageInstallActionsAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressCountDisplay due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ScheduleConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: ValidationTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StopPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CachePatchPage due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: InitializeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: MsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeMsiAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PostMsiTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: DowntimeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartPatchedServices due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: StartupTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: PreUninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UninstallTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: UpgradeMsiTimingAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: FinalizeTimingConfigAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: CreateARPRegKeyAction due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Skipping Action: NotifyProgressComplete due to user cancel request
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: FinalizeProgressStatus
2013-03-07 20:18:59 Slp: Completed Action: FinalizeProgressStatus, returned True
2013-03-07 20:18:59 Slp: ----------------------------------------------------------------------
2013-03-07 20:18:59 Slp: Running Action: CloseUI
2013-03-07 20:18:59 Slp: Stop action skipped in UI Mode Full
2013-03-07 20:18:59 Slp: Completed Action: CloseUI, returned True
2013-03-07 20:19:00 Slp: Received request to add the following file to Watson reporting: C:\Users\cwsmain\AppData\Local\Temp\tmp29B5.tmp
2013-03-07 20:19:00 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-03-07 20:19:00 Slp: Inner exceptions are being indented
2013-03-07 20:19:00 Slp:
2013-03-07 20:19:00 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
2013-03-07 20:19:00 Slp:     Message:
2013-03-07 20:19:00 Slp:         Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:     Stack:
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.GetInputSettingValue(String settingName)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteInputSettings(LogProviderSummaryFile summaryLog)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WritePatchSummaryLog(Int32 resultCode, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.StatusLogs.WriteSummaryLog(Int32 resultCode, Boolean finalResult, Exception exception)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.WriteStatusLogs(Int32 resultCode, Exception e)
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Start()
2013-03-07 20:19:00 Slp:         at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
2013-03-07 20:19:00 Slp:     Inner exception type: System.Runtime.InteropServices.ExternalException
2013-03-07 20:19:00 Slp:         Message:
2013-03-07 20:19:00 Slp:                 Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\ebms87n0.cmdline".
2013-03-07 20:19:00 Slp:         Stack:
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.Executor.ExecWaitWithCapture(SafeUserTokenHandle userToken, String cmd, String currentDir, TempFileCollection tempFiles, String& outputName, String& errorName, String trueCmdLine)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.Compile(CompilerParameters options, String compilerDirectory, String compilerExe, String arguments, String& outputFile, Int32& nativeReturnValue, String trueArgs)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromFileBatch(CompilerParameters options, String[] fileNames)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromSource(CompilerParameters options, String[] sources)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
2013-03-07 20:19:00 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject(String rootPath, Type type, String elementXPath)
2013-03-07 20:19:45 Slp: Watson Bucket 1
 Original Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.DeserializeObject

2013-03-07 20:19:45 Slp: Parameter 2 : System.CodeDom.Compiler.Executor.ExecWaitWithCaptureUnimpersonated

2013-03-07 20:19:45 Slp: Parameter 3 : Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : System.Runtime.InteropServices.ExternalException@267

2013-03-07 20:19:45 Slp:
 Final Parameter Values

2013-03-07 20:19:45 Slp: Parameter 0 : SQL2008@RTM@KB2630458

2013-03-07 20:19:45 Slp: Parameter 1 : 0x055C02AC

2013-03-07 20:19:45 Slp: Parameter 2 : 0x86203738

2013-03-07 20:19:45 Slp: Parameter 3 : 0xDF039760@1201@1

2013-03-07 20:19:45 Slp: Parameter 4 : 0xD95CEA3F

2013-03-07 20:19:45 Slp: The following exception occurred while preparing status logs during Watson failure processing: Cannot execute a program. The command being executed was "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\csc.exe" /noconfig /fullpaths @"C:\Users\cwsmain\AppData\Local\Temp\edxytlec.cmdline".
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-03-07 20:19:45 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130307_200912\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2013-03-07 20:19:46 Slp: The following exception occurred during Watson failure processing: The directory is not empty.

2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: ----------------------------------------------------------------------
2013-03-07 20:19:46 Slp:
2013-03-07 20:19:46 Slp: Error result: -2068774911
2013-03-07 20:19:46 Slp: Result facility code: 1201
2013-03-07 20:19:46 Slp: Result error code: 1

Hello there!

I installed the released SQL Server 2008 R2 on x64 (amd64) computer running Windows Server 2008 R2. This was a full install with all the setup features selected in the Setup Wizard. Setup process has finished successfully. However, after a reboot I discovered that the SQL Server (INSTANCENAME) is not running. I tried to forcibly start the service from the service properties dialog using the Services snap-in. Starting the service returned the following error:

---------------------------
Services
---------------------------
Windows could not start the SQL Server (KL) service on Local Computer.



Error 1067: The process terminated unexpectedly.


---------------------------
OK  
---------------------------

The service is running under the Network Service account selected during the setup process.

In the Application log is see the following error:

Faulting application name: sqlservr.exe, version: 2009.100.1600.1, time stamp: 0x4bb6b40b
Faulting module name: sqlservr.exe, version: 2009.100.1600.1, time stamp: 0x4bb6b40b
Exception code: 0xc0000005
Fault offset: 0x00000000000a1c61
Faulting process id: 0x17dc
Faulting application start time: 0x01cb0ec3a63f6646
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.KL\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.KL\MSSQL\Binn\sqlservr.exe
Report Id: e4335a09-7ab6-11df-91cf-0023544cc96e

From the Sql Server Configuration Manager I see that the SQL Server (KL) instance has the automatic startup mode and the state is Stopped.

I have disabled all the client protocols but TCP/IP. My firewall is turned off.

Starting the SQL Server (KL) service from the SQL Server Configuration Manager returns this error:

---------------------------
SQL Server Configuration Manager
---------------------------
The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details.
---------------------------
OK  
---------------------------

I figured out that I DON NOT HAVE THE DATA folder under the MSSQL10_50.KL folder.

That's all I have:

18.06.2010  12:04    <DIR>          .
18.06.2010  12:04    <DIR>          ..
18.06.2010  12:04    <DIR>          Binn
18.06.2010  12:04    <DIR>          FTData
18.06.2010  10:45    <DIR>          Install
03.04.2010  21:59            14 176 sql_engine_core_inst_keyfile.dll
03.04.2010  10:59            14 176 sql_fulltext_keyfile.dll
18.06.2010  10:45    <DIR>          Upgrade

Seems like this wasn't a success setup despite what setup wizard reported. Or I am missing something?

Any clues?

Thank you in advance.

Regards,

Stanislav.

Hi All,

Urgently need advice on a network speed limitation in a domain network environment.

I have a brand new server installation running MS Windows Server 19. The third party software VMaster using the SQL database was installed by there company. (Im a SQL beginner)

on this network there are 10 pc that running the VMaster (the program) that needs to access the SQL database on the server.

Occasionally and with no apparent pattern different computers are reduced to a network traffic of no more than 2MB/s. While the pc is limited like this i can copy any other files over the network with full speed, it only limits the SQL traffic. This behavior is seen over the whole network with all machines but not simultaneously.  one might be limited the rest work fine, then 3 might be limited the rest work fine. all might be limited. and with no apparent reason the limitation is lifted and the pc works fine again.

The VMaster support is ambient that it has nothing to do with them. I how suspect that there might be a setting in SQL that dose this. 

Any advice will be appreciated.

Hello There,

 Kindly advise me pointer and useful inputs, views to consider on the SQL Server 2012 consolidation and Rationalization.

 In our environment there are 40 SQL Server Instances running. Business like to consolidate them as much as possible.

1 Where to start

2. what are the criteria,

3. how to assess the current performance

4. how to validate to ensure in terms performance and security post consolidation

Thanks, Siva SQL

Sivaprasad S http://sivasql.blogspot.comPlease click the Mark as Answer button if a post solves your problem!

Hi All ,

I am trying an automated install of SQL SERVER 2014 ENTERPRISE EDITION with below Features :

FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS

OS detail : Windows Server 2008 R2

SQL Server : SQL SERVER 2014 ENTERPRISE EDITION 

Below are the contents of Summary.txt :

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068578304
  Exit facility code:            1204
  Exit error code:               0
  Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
  Start time:                    2016-04-19 04:34:35
  End time:                      2016-04-19 04:35:22
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for MDS:             SQL Server Setup was canceled before completing the operation. Try the setup process again.


Machine Properties:
  Machine name:                  DENCITS03
  Machine processor count:       1
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered  Configured
  SQL Server 2005      JDESSELOCAL          MSSQL.1                        Database Engine Services                 1033                 Express Edition      9.4.5000        No         Yes       
  SQL Server 2005      JDESSELOCAL          MSSQL.1                        SharedTools                             1033                 Express Edition      9.4.5000        No         Yes       
  SQL Server 2005                                                          Tools                                   1033                 Express Edition      9.1.2047        No         Yes       
  SQL Server 2005                                                          ToolsClient                             1033                 Express Edition      9.1.2047        No         Yes      

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         Z:\Downloads\en_sql_server_2014_enterprise_edition_x64_dvd_3932700\x64\setup\
  Installation edition:          Enterprise

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
  AGTSVCPASSWORD:                <empty>
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            DENCITS03\ITS03
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   SQL2014Controller
  CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
  CLTSTARTUPTYPE:                Manual
  CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               Manual
  CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     DENCITS03\ITS03
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
  FILESTREAMLEVEL:               3
  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:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT Service\MsDtsServer120
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              SharePointFilesOnlyMode
  RSSVCACCOUNT:                  NT Service\ReportServer
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DENCITS03\ITS03
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

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

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

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

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Rules with failures:

Global rules:

Scenario specific rules:

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

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

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
    Message: 
        The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
    HResult : 0x84b40000
        FacilityCode : 1204 (4b4)
        ErrorCode : 0 (0000)
    Data: 
      SQL.Setup.FailureCategory = InputSettingValidationFailure
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
        at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
        Message: 
                The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
        HResult : 0x87d00006
                FacilityCode : 2000 (7d0)
                ErrorCode : 6 (0006)
        Data: 
          DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
          SettingName = CLTRESULTDIR
          WatsonData = Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Below are the contents of ConfigurationFile.ini :

;SQL Server 2014 Configuration File
[OPTIONS]

; Required to acknowledge acceptance of the license terms.
IACCEPTSQLSERVERLICENSETERMS="True"

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 

ACTION="Install"

; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 

ENU="True"

; Setup will not display any user interface. 

QUIET="True"

; Setup will display progress only, without any user interaction. 

QUIETSIMPLE="False"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 

UpdateEnabled="True"

; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 

ERRORREPORTING="False"

; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 

USEMICROSOFTUPDATE="False"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 

FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS

; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services. 

UpdateSource="MU"

; Displays the command line parameters usage 

HELP="False"

; Specifies that the detailed Setup log should be piped to the console. 

INDICATEPROGRESS="False"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 

X86="False"

; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 

INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"

; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 

INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"

; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS). 

INSTANCENAME="MSSQLSERVER"

; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 

SQMREPORTING="False"

; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 

INSTANCEID="MSSQLSERVER"

; The computer name that the client communicates with for the Distributed Replay Controller service. 

CLTCTLRNAME="SQL2014Controller"

; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 

CTLRUSERS="Domain\user"

; The account used by the Distributed Replay Controller service. 

CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"

; The startup type for the Distributed Replay Controller service. 

CTLRSTARTUPTYPE="Manual"

; The account used by the Distributed Replay Client service. 

CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"

; The startup type for the Distributed Replay Client service. 

CLTSTARTUPTYPE="Manual"

; The result directory for the Distributed Replay Client service. 

CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"

; The working directory for the Distributed Replay Client service. 

CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"

; RSInputSettings_RSInstallMode_Description 

RSINSTALLMODE="DefaultNativeMode"

; RSInputSettings_RSInstallMode_Description 

RSSHPINSTALLMODE="SharePointFilesOnlyMode"

; Specify the installation directory. 

INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

; Agent account name 

AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"

; Auto-start service after installation.  

AGTSVCSTARTUPTYPE="Manual"

; Startup type for Integration Services. 

ISSVCSTARTUPTYPE="Automatic"

; Account for Integration Services: Domain\User or system account. 

ISSVCACCOUNT="NT Service\MsDtsServer120"

; The name of the account that the Analysis Services service runs under. 

ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"

; Controls the service startup type setting after the service has been created. 

ASSVCSTARTUPTYPE="Automatic"

; The collation to be used by Analysis Services. 

ASCOLLATION="Latin1_General_CI_AS"

; The location for the Analysis Services data files. 

ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"

; The location for the Analysis Services log files. 

ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"

; The location for the Analysis Services backup files. 

ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"

; The location for the Analysis Services temporary files. 

ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"

; The location for the Analysis Services configuration files. 

ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"

; Specifies whether or not the MSOLAP provider is allowed to run in process. 

ASPROVIDERMSOLAP="1"

; Specifies the list of administrator accounts that need to be provisioned. 

ASSYSADMINACCOUNTS="Domain\user"

; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 

ASSERVERMODE="MULTIDIMENSIONAL"

; CM brick TCP communication port 

COMMFABRICPORT="0"

; How matrix will use private networks 

COMMFABRICNETWORKLEVEL="0"

; How inter brick communication will be protected 

COMMFABRICENCRYPTION="0"

; TCP port used by the CM brick 

MATRIXCMBRICKCOMMPORT="0"

; Startup type for the SQL Server service. 

SQLSVCSTARTUPTYPE="Automatic"

; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 

FILESTREAMLEVEL="3"

; Name of Windows share to be created for FILESTREAM File I/O. 

FILESTREAMSHARENAME="MSSQLSERVER"

; Set to "1" to enable RANU for SQL Server Express. 

ENABLERANU="False"

; Specifies a Windows collation or an SQL collation to use for the Database Engine. 

SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"

; Account for SQL Server service: Domain\User or system account. 

SQLSVCACCOUNT="NT Service\MSSQLSERVER"

; Windows account(s) to provision as SQL Server system administrators. 

SQLSYSADMINACCOUNTS="Domain\User"

; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication. 

SECURITYMODE="SQL"

; Specify 0 to disable or 1 to enable the TCP/IP protocol. 

TCPENABLED="1"

; Specify 0 to disable or 1 to enable the Named Pipes protocol. 

NPENABLED="0"

; Startup type for Browser Service. 

BROWSERSVCSTARTUPTYPE="Automatic"

; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 

RSSVCACCOUNT="NT Service\ReportServer"

; Specifies how the startup mode of the report server NT service.  When 
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled 

RSSVCSTARTUPTYPE="Automatic"

; Add description of input argument FTSVCACCOUNT 

FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

Please guide me where i am going wrong in this whole process.

Thanks...

As title, do you have any idea for changing default installation path for configuration file?

The default path is C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\2019_0723_883984\Configuration file.init but I want to change this path.

Thank you

Hi,

I am going to remove an app server that has DB on dedicated (shared with others DBs) SQL server.

So my plan is :

1. Remove app server.

2. In visual studio of SQL server right click\delete the DB of removed app server.

Do I need to perform any other actions?

Thx.

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Hi,

This strange behavior started recently. If I close SSMS, it restarts itself as if it crashed and trying to restore itself. Even if I hit cancel as it's restarting, it will restart itself yet again. This happens twice. Any idea what's causing this?

Thanks, Sam