I've installed SQL Server 2016 on Win 10 laptop for testing and development use.  After restarting the pc the sql services do not restart.  They have a login failure, and if if delete the password for each service, the password is repopulated automatically and then I can start the service. 

The user name of the SQL Server service is "NT Service\MSSQLSERVER"

Any thoughts on how to make these passwords stay?

For over a week, at least 6 attempts to install KB3164398 have failed during Windows Update:

Critical Update for SQL Server 2016 MSVCRT Prerequisites KB3164398 - Error 0x80070643

This is blocking other needed updates from coming down.

How do I get this "road block" out of the way until Microsoft can find the time to withdraw it and replace it with one that will actually install?

If you think development is tough now, think how hard it was using punched cards :-)

I want to install SQL Server 2016 now SQL Server 2014 is already installed .

Now what will be the way uninstall sql server 2014 then install Sql Server 2016 or ...?

I have installed visual studio 2015 and used it to write a program ,, that program require a database and by default the version installed to deal with that was sql 2016 localdb ,, 
after finishing the program and after publishing it 
i find out that i can't install the sql server 2016 express or the localdb on x32 bit machine 

there is no notice on this before installing and it's not mentioned in the requirement field at the installation page 

correct me if i'm wrong

Hi,

I'm facing an SQL Server setup errors.

• Cause of feature error:
  An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  
  
• Error details:
  $ Installing error for SQL Server set up file
  Overlapped I/O operation is in progress.
  error code: 997

I googled and find some articles saying that "Overlapped I/O operation is in progress." error causes from KB2918614. However the KB is not installed on my machine.

Could someone please tell me where this error comes from?

Thank you in advance.
Saki

Melissa Explore Information Services, LLC

Hi,

I am trying to install SQL Server 2012 and 2014 but have been having so much difficulty. I actually installed server 2012 earlier last year but I gone and deleted some folders related to the sql server. Now, I am trying to re-install server 2012 and trying 2014 but it gives the same error for both installations: 

Would really appreciate all the help I can get. I've been grieving over this issue for a while now.

Hi

I have on multiple occasions tried to install SSIS but I get the following error code:

I tracked down the installation log which I have copied below. The error I have highlighted in bold.

It looks like I have a newer version installed but I am not sure how that can be the case as this error occurred the first time I tried to install SQL Server 2016. I have tried uninstalling SQL Server and reinstalling a new instance but I get the same message. Have also tried the 32 bit and 63 bit versions of the installer.

To be honest my IT knowledge is relatively low so I am not sure where I am going wrong and any help would be greatly appreciated.

Cheers

Hamish

Hi,

I have a Active Passive cluster setup. I would like to disable all network protocols except TCP/IP. Is there any risk?

And I think we can make the change in Each node's configuration manager, first passive node and do failover then on the other node, please correct me if I am wrong. Any article which explains this scenario.

Thanks,

Ashru

MCTS, http://asharafaliptb.wordpress.com

Dears,

i have SQL Server 2014 Std edition, installed over two virtual machines,

my virtualization platform is ESX 5.5 clustered, my question is can i configure SQL VMs to be a high available VMs over VMware?

which means i want to configure the SQL virtual machines to fail over to any other host in case of failure.

i would appreciate if any one can share with me a link describing this issue.

Samer F. Mustafa Microsoft Technical Team Leader. sf_mustafa@hotmail.com

Hi all,

I have a Windows 2008 R2 box running SQL 2008 R2 64 bit.

I have 44 Gigs of RAM installed on my server..I have installed SQL server 2008r2 with 5 instance(One default+4 named instances) and SQL is using 43.8 Gigs of the RAM according to Task Manager.

Is this normal? if not  please provide solution for reducing memory usage.

Thank you,

Raj

Good evening all,

Im trying to install SQL 2016 enterprise edition on windows 2012 r2 datacenter.

though i followed all the steps and installed all the prerequisites i'm getting below error.

(Error KB2919355)

even after restarting server and trying to install but same error:

steps i followed downloaded and installed belolw.

1. Clearcompressionflag.exe38 KB

2. Windows8.1-KB2919355-x64.msu690.8 MB
3. Windows8.1-KB2932046-x64.msu48.0 MB
4. Windows8.1-KB2959977-x64.msu2.8 MB
5. Windows8.1-KB2937592-x64.msu303 KB
6. Windows8.1-KB2938439-x64.msu19.6 MB
7. Windows8.1-KB2934018-x64.msu126.4 MB

Thanks,

Vijay

Missing system administration account.  To continue provide at least one window account to provision as a sql server system admistrator.

error message at server configuration.  After i hit next.  I really need some help and dont know what to do with the passwords and accounts.

I am in it deep

Jim

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...

I just attempted installing SQL 2016 RTM and the install rebooted the server. After the reboot SQL of course is not working at all due to the install not completing; so, it's hosed up.  It appears that msiexec requested a restart due to SSIS (see below).  Has anyone had this issue?  This is a new Win 2012-R2 VM and a new SQL 2016 install.

From the Win App Error Log:

Windows Installer requires a system restart. Product Name: SQL Server 2016 Integration Services. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 1. Reason for Restart: 1.

In a new installation of SQL Server 2008R2 Standard in a windows Server2012R2, we have mixed-mode authentication enabled. Using Windows authentication, we are able to authenticate using SQL Management Studio as expected. Using SQL authentication, SQL Management Studio will not let me authenticate. Two strange symptoms:

• Typing in the password field on the SQL Management Studio Connect To Server dialogue has a long lag of about 3 seconds per character typed
• Authentication fails, even though the password is entered correctly

Using SQL Authentication and using another SSMS that is installed in a different server we are able to connect to the instance.

Any Idea in what to do in this cases?

I am trying to install Microsoft SQL Server 2008R2 in Windows 10 Operating System.

After the initial steps, I see this error, when I get into the main part of the installation:

--------------------------------

TITLE: SQL Server Setup failure

SQL Server Setup has encountered the following error:

There was an error generating the XML document.

Error code 0x84B10001.

--------------------------------

I have installed service pack 3 for SQL Server 2008 R2 already, and have also installed Cumulative Update package 5 for SQL Server 2008 R2.

Is there any quick solution you can provide me ? I need to sort this out ASAP.

Hi, all

I have a licensing question for you. We have a Select Agreement (actually, an Enterprise Agreement) which includes SQL Server (2000, 2005, 2008). Some of us also have MSDN licenses. The MSDN versions may have been installed onto production servers. Is it possible to change the license number from that of the MSDN to our SA? I want to check to make sure that all of our production servers have the SA license number and not the MSDN so that we're in compliance.

Perhaps the broader question is whether or not it even matters. Does the license number in the software make a difference if we are paid up and licensed through the SA or EA?

Also, is the media/installation any different? I expect that the MSDN and Volume Licensing versions would be the same. It would be awful if we would have to re-install.

Again, I want to make sure that we're in compliance and won't hurt ourselves down the road. Thanks a ton!

Brian

Sr. DBA