hi there,i am trying to install sql server 2014 developer edition in windows 8.1.Byt I am getting the error.The program can't start because the sqlsetupbootstrapper.dll is missing in your computer and I also found that this dll is available in the .iso file of the server downloaded from Microsoft.

Sumit Bhargav

benmarshall

Im running a Windows 10 laptop with an i7 processor, plenty of memory and SSD.

When i return some rows using SSMS 2012 (also have Visual Studio 2015 installed) it take approximately 5 seconds for the data to return. Is there any reason why or anyway that i can narrow down what the issue may be?

Environment

Our machine is running Windows Server 2012 R2 Standard and SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86).

Problem encountered

When installing the update for KB3045313 in Windows Update, the following error was prompted (error screen attached):

Error(s) found:

Code 80246013 Windows Update ran into a problem.

Then I tried to download the update from Microsoft and install the update manually, the following error was prompted (error screen attached):

The following feature couldn't be installed:

.NET Framework 3.5 (includes .NET 2.0 and 3.0)

As .NET framework is not compulsory for SQL Server 2008 R2, how can we install the update for KB3045313 when SQL Server development using NET Framework 3.5 is not required for us.

Trying to view stored procedure on Azure SQL Server via SSMS and now getting this error message. I know this has been mentioned elsewhere - http://stackoverflow.com/questions/27690417/ssms-sql-azure-v12-preview-unknown-property-isnativelycompiled - but the solution seems to have been to install a patch on the server! So presumably this means Azure have to install the patch.

----------

The image (if I were allowed to add it!) would say this:

----------

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

Additional information:

unknown property IsNativelyCompiled (Microsoft.SqlServere.Management.Sdk.Sfc)

hi

I am using sharepoint 2013, and sql server 2014 in two seprate servers,

now I have to update sqlserver 2014 to latest version, would you please help me about the steps?

forexample : 1- full backup 2- stop service ...

I am new in sharepoint and sql server am iam worry

thanks

I have Signed up for SQL sever on Linux evaluation.

On March 16th, I received a download link from SQL server community for release candidate of SQL Server 2016.

But the link takes me to regular SQL server download page.

Was anyone able to successfully install SQL server on linux using the link provided in community newsletter?

I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.

Any ideas?

Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htm

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

Hi,

I work at a 3 people start up. None of us are IT guys. I know some SQL and would like to use it for some of our reporting needs. We work in one of those shared office spaces but we do have our own shared network. We use a cloud service to share files. When I click on "Network" on Windows Explorer I can see the machines of my other two co-workers (although I have never connected to their machines)

Sql server is installed locally on my machine and I would like to give read-access to the DB to my co-workers so they can view the SSRS reports I created. I tried to create a Login for one of the users but the only location that's available to me is my own machine. Is this even possible in our current set-up or am I completely on the wrong track here? Is it simply a matter of getting their Windows userid and pw and connecting to their machine?

Hi all,

i am facing the below issue and get the below log details.

Hello,

I need to install SQL Server 2014 business intelligence with SP1 for educational purposes. I have uninstalled the previously installed instance of SQL Server to install a new and clean BI version. To uninstall the previous version I used IObit uninstaller which also deletes all remaining folders and registers.

When I try to boot the setup.exe of the BI version I get an empty error box. I get the same  when trying to install other versions of SQL server.

After doing some research about this error, I found that capsol.exe should be able to resolve the issue. So I tried the command:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\capsol.exe -machine -reset

and

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\capsol.exe -machine -reset

unfortunately, both did not resolve the issue. I tried every other possible solution on the source thread (SQL Server 2008 R2 setup.exe will not run) without success.

Please help me to solve this problem

Kind regards, Wessel

Hi,

I am new to SQL and I am not sure if this is in the correct thread but here goes anyway.

We have a Virtual Machine which has SQL server running inside it, the VM currently has 16 vCPU assigned to it, and two SQL instances. we are licensed for 16 cores and each instance is left in its default configuration to balance the CPU usage itself, we don't tie any cores to an instance.

The following link states Limited to lesser of 4 Sockets or 16 cores https://technet.microsoft.com/en-us/library/ms143760(v=sql.110).aspx my question is this: If we assigned 20 vCPU to the VM will SQL only use 16 of them? I guess this is easy to see in task manager if we had one instance, but we have two instances which aren't tied to any cores, so is it possible that instance A will use 16 of 20 cores, and instance B will use a different 16 of 20 cores (with some crossover). What we are trying to avoid is breaking any licensing rules, and also learn how SQL technically uses cores? will the SQLServer.exe process of each instance only have its affinity set to 16 of the cores for example?

Would someone be able to explain this to me, we dont have spare resources to perform a test environment using more than 16 cores, so it's tricky for us to find this out ourselves unless we bring the live system down and assign more cores.

the reason behind this is we think the number of vCPU assigned might be having a bit of a performance impact on the server, but without knowing how each instance balances across the cores and whether we will break licensing rules, it is difficult to move forwards.

Many thanks

Steve

I'm about to set up a new SQL failover cluster and plan to put the tempdb files on shared storage.

The following page states this will be supported: https://msdn.microsoft.com/en-us/library/mt683723.aspx

But this page states it won't: https://msdn.microsoft.com/en-us/library/ms143506.aspx#StorageTypes

Which is correct?  Thanks

This page implies Windows 2012 is not supported for a SQL 2016 cluster.

https://msdn.microsoft.com/en-us/library/ms189910.aspx?f=255&MSPPError=-2147217396

Is this correct?

I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.

Any ideas?

Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htm