Hi, I have a Windows server 2008 R2 in production environment and a SQL server 2008 R2 there. Windows server had a windows update few days back (KB4457008 and KB4462923) and a server reboot following that. After the reboot, SQL service was not starting in the server with an event viewer error, Unable to access MSSQL\ERRORLOG file. I found ERRORLOG file in MSSQL folder has changed to Read-Only state and hence SQL Server Service was not starting. It started successfully by creating a new ERRORLOG file once we renamed the existing ERRORLOG file to some other name.

I got an updatefrom the forum itself, for my query on root cause of this incident as "Someone either manually changed the SQL Server service account (without using configuration manager, which would set the rights automatically) or the rights on the directory were changed manually.  Those changes do not take effect until a reboot." (Thread Link : https://social.msdn.microsoft.com/Forums/en-US/3151c239-41c1-47b0-9da4-53c40c61e2dd/issue-with-starting-sql-server-service?forum=sqlsetupandupgrade)

Now I have a query on this reboot statement..

I have tested this in a local system,  I made the Errorlog file there Read-only (manually checked Readonly property) and once I stopped the SQL SERVER service and tried to start, it failed.. It got affected without a system reboot.

Can anyone please help me to have a clarification on this..

Thanks in Advance

Karthika

Hello all.

I am attempting to install KB4464106 on this installation:

Microsoft SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64)   Sep 13 2018 22:16:01   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor) 

and I am presented with the following error during the upgrade:

There are no SQL Server instances or shared features that can be updated on this computer.

This error is specific to this machine as I am able to update other machines that were at this same patch level. Does anyone know why this would be or how to force and upgrade?

Thanks all.

I'm upgrading from a gen 12 dell server with a single raid 10 solid state array to a gen 14 with 3 solid state and 1 spinning arrays and am wondering which needs the better performance, temp tables or transaction log and if my idea is a good idea or just crazy...

Array number 1 is a dell BOSS controller card with mirrored 240GB SATA M.2 SSD's @ 6Gbps

Array's 2 & 3 are running on the same PERC H740P RAID Controller with 8GB NV Cache

Array number 2 is 4 - 480GB SSD SAS Mix Use 12Gbps 512n RAID 10

Array number 3 is 4 - 1.2TB 10K RPM SAS 12Gbps 512n RAID 5

Array number 4 is yet to be defined as either RAID 0 or RAID 1 and is 2 - 800GB, NVMe, Mixed Use Express Flash (2.5 SFF Drive, U.2, PM1725a) running at 8.0 GT/s.  RAID will be software defined.

Array #1 will host the operating system and page file.  Array #3 will just be used for backups etc.

My understanding is that splitting the various db files (mdf, ldf & tmp tables) onto as many different physical buses as possible is how to best maximize speed beyond a single ssd array so my thought was to put the mdf onto array #2, the ldf onto array #1 and the tmp tables onto array #4 in raid 0.

Question 1: Is it OK to put tmp tables onto raid 0?  I assume if one drive fails causing the array to break, sql will just shut down with errors but not actually lose anything since it's not the mdf or ldf?  I'm having a hard time finding anything that says either way on this. 

Question 2: If putting the tmp tables onto RAID 0 is a bad idea, what about just running it in RAID 1?  Obviously it won't be as fast as array #2 but it should still be significantly faster than trying to run both the mdf and tmp tables on array 2 right?

Question 3: Similar to Question 2...I realize array #2 is faster than array #1 as well but splitting the LDF onto it's own physical pci channel (array #1) should be faster than putting them both on array #2 right?

Question 4: If I'm completely crazy for considering this layout, what would be the best layout on the given hardware?

Thanks in advance for any advice!

ERROR LOG CONTENTS BELOW:

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2061893608
  Exit facility code:            1306
  Exit error code:               24
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2010-08-16 14:52:16
  End time:                      2010-08-16 15:24:53
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\Detail.txt
  Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xE53883A0%400xBE03358B%401306%4024

Machine Properties:
  Machine name:                  MICHAEL-PC
  Machine processor count:       2
  OS version:                    Windows 7
  OS service pack:              
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x86
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL Server 2008 R2
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         F:\x86\setup\
  Installation edition:          STANDARD

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      True
  AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            Michael-PC\Michael
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\ConfigurationFile.ini
  CUSOURCE:                     
  ENABLERANU:                    False
  ENU:                           True
  ERRORREPORTING:                False
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
  FTSVCPASSWORD:                 *****
  HELP:                          False
  IACCEPTSQLSERVERLICENSETERMS:  False
  INDICATEPROGRESS:              False
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  NPENABLED:                     0
  PASSPHRASE:                    *****
  PCUSOURCE:                    
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Michael-PC\Michael
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  False
  TCPENABLED:                    1
  UIMODE:                        Normal
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\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:      0xBE03358B@1306@24
  Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\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:      0xBE03358B@1306@24
  Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\Detail.txt

  Feature:                       Full-Text Search
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xBE03358B@1306@24
  Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\Detail.txt

  Feature:                       Analysis Services
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Reporting Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0xBE03358B@1306@24
  Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100816_145006\Detail.txt

  Feature:                       Integration Services
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Management Tools - Complete
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Client Tools SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Business Intelligence Development Studio
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Books Online
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Microsoft Sync Framework
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

Rules with failures:

Global rules:

Scenario specific rules:

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

HI Everyone,

i have a 1Tb database i want to move it from lower version to higher version with out downtime, any suggestion.

what is the better approach.

Thanks,

Lokesh vankam.

Hi,

I am planning for SQL Server consolidation, pls guide me what would be steps, what are consideration. can you pls share questionnaire to collect information before starting sql server consolidation project.

Thx

iffi

Hi,

Is there any Workarround to  install SSMS 18 on Windows server 2012 R2 ?

Since a couple a day, t tried to install sql server 2017 Dev on Win 10.  Everything installs fine but except 2 components "Client Tools Sdk" and "Client Tools Backwards Compatibility".    <o:p></o:p>

Before installation, I removed sql server 2014, 2016, ssdt for vs2015/17.   In the log, I see i have a problem of dependency, I am not able to understand.    <o:p></o:p>

Could you help me solve this issue?

verall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068643839
  Start time:                    2017-11-17 07:11:03
  End time:                      2017-11-17 07:12:41
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  CDM0001
  Machine processor count:       8
  OS version:                    Microsoft Windows 10 Enterprise N (10.0.16299)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2014                                                          Client Tools Backwards Compatibility     1033                                      12.2.5000.0     No         Yes       
  SQL Server 2014                                                          Client Tools SDK                         1033                                      12.2.5000.0     No         Yes       
  SQL Server 2016                                                          SSMS                                                                               13.0.16106.4    No         Yes       
  SQL Server 2016                                                          Client Tools Backwards Compatibility     1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools SDK                         1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          LocalDB                                  1033                 Express Edition      13.1.4001.0     No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                Database Engine Services                 1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                SQL Server Replication                   1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                Full-Text and Semantic Extractions for Search 1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                Data Quality Services                    1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                PolyBase Query Service for External Data 1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                Machine Learning Services (In-Database)  1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                AdvancedAnalytics\sql_inst_mr            1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSSQL14.SQL2017                AdvancedAnalytics\sql_inst_mpy           1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017      SQL2017              MSAS14.SQL2017                 Analysis Services                        1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Client Tools Connectivity                1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Data Quality Client                      1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Integration Services                     1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Scale Out Master                         1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Scale Out Worker                         1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Master Data Services                     1033                 Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Machine Learning Server (Standalone)                          Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          R                                                             Developer Edition    14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Python                                                        Developer Edition    14.0.1000.169   No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         F:\x64\setup\
  Installation edition:          Developer

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 <empty>
  AGTSVCPASSWORD:                <empty>
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171117_071103\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SDK
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    SQL2017
  INSTANCENAME:                  SQL2017
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          <empty>
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 <empty>
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           <empty>
  SQLTELSVCACCT:                 <empty>
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          0
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            0
  SQLTEMPDBFILEGROWTH:           -1
  SQLTEMPDBFILESIZE:             -1
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        -1
  SQLTEMPDBLOGFILESIZE:          -1
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171117_071103\ConfigurationFile.ini

Detailed results:
  Feature:                       Client Tools SDK
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171117_071103\SystemConfigurationCheck_Report.htm

01) 2017-11-17 07:11:48 Slp: Running Action: MsiTimingAction
(01) 2017-11-17 07:11:48 Slp: ----------------------------------------------------------------------
(01) 2017-11-17 07:11:48 Slp: Running Action: Install_sql_tools_extensions_Cpu64_Action
(01) 2017-11-17 07:11:48 Slp: SetFeaturePropsModifyInstallAction for sql_tools_extensions_Cpu64 
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\RefCount\sql_tools_extensions14
(01) 2017-11-17 07:11:48 Slp: Sco: File 'F:\x64\setup\x64\sql_tools_extensions.msi' does not exist
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\14.0
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to get registry value InstallDir
(01) 2017-11-17 07:11:48 Slp: Sco: File 'F:\x64\setup\x64\sql_tools_extensions.msi' does not exist
(01) 2017-11-17 07:11:48 Slp: Sco: File 'F:\x64\setup\x64\sql_tools_extensions.msi' does not exist
(01) 2017-11-17 07:11:48 Slp: Checkpoint: PREINSTALL_SQL_TOOLS_EXTENSIONS_CPU64_ACTION
(01) 2017-11-17 07:11:48 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open SC Manager
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to open service handle for service msiserver
(01) 2017-11-17 07:11:48 Slp: Invoking QueryServiceStatus Win32 API
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to close service handle for service msiserver
(01) 2017-11-17 07:11:48 Slp: Sco: Attempting to close SC Manager
(01) 2017-11-17 07:11:48 Slp: Target package: "F:\x64\setup\sql_tools_extensions.msi"
(01) 2017-11-17 07:12:37 Slp: InstallPackage: MsiInstallProduct returned the result code 1602.
(01) 2017-11-17 07:12:37 Slp: No retry-able MSI return code detected.
(01) 2017-11-17 07:12:37 Slp: Error: Action "Install_sql_tools_extensions_Cpu64_Action" failed during execution.
(01) 2017-11-17 07:12:37 Slp: Completed Action: Install_sql_tools_extensions_Cpu64_Action, returned False
(01) 2017-11-17 07:12:37 Slp: Attempting to pause the 32 bit ngen queue for x64
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:37 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:37 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(06) 2017-11-17 07:12:37 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(06) 2017-11-17 07:12:37 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(06) 2017-11-17 07:12:37 Slp: 
(06) 2017-11-17 07:12:37 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:37 Slp: Process returned 0
(01) 2017-11-17 07:12:37 Slp: Attempting to pause the 64 bit ngen queue
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:37 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:37 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(06) 2017-11-17 07:12:37 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(06) 2017-11-17 07:12:37 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(06) 2017-11-17 07:12:37 Slp: 
(06) 2017-11-17 07:12:37 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:37 Slp: Process returned 0
(01) 2017-11-17 07:12:37 Slp: Action "Install_sql_tools_extensions_loc_Cpu64_1033_Action" will return false due to the following conditions:
(01) 2017-11-17 07:12:37 Slp: Condition "Validate feature dependencies for package: sql_tools_extensions_loc_Cpu64_1033. The condition ensures that at least one of the features to be changed has its dependencies satisified." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:37 Slp: Checking the state of all features the package depends on.
(01) 2017-11-17 07:12:37 Slp: Condition "Feature dependency condition for action: Install_sql_tools_extensions_loc_Cpu64_1033_Action, the condition tests feature: SDK_Full_Extensions_Loc_sql_tools_extensions_loc_Cpu64_1033. There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:37 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:37 Slp: Condition "Feature dependency condition for action: Install_sql_tools_extensions_loc_Cpu64_1033_Action, the condition tests feature: SDK_FLS_Extensions_sql_tools_extensions_loc_Cpu64_1033. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:37 Slp: Condition is false because the required feature SDK_Full_Extensions_Loc_sql_tools_extensions_loc_Cpu64_1033 failed in result Result
(01) 2017-11-17 07:12:37 Slp: Condition will fail because no feature has any satisifed dependencies.
(01) 2017-11-17 07:12:37 Slp: Attempting to pause the 32 bit ngen queue for x64
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:37 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:37 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(18) 2017-11-17 07:12:37 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(18) 2017-11-17 07:12:37 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(18) 2017-11-17 07:12:37 Slp: 
(18) 2017-11-17 07:12:37 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:37 Slp: Process returned 0
(01) 2017-11-17 07:12:37 Slp: Attempting to pause the 64 bit ngen queue
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:37 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:37 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:37 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(19) 2017-11-17 07:12:38 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(19) 2017-11-17 07:12:38 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(19) 2017-11-17 07:12:38 Slp: 
(19) 2017-11-17 07:12:38 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:38 Slp: Process returned 0
(01) 2017-11-17 07:12:38 Slp: Action "Install_sql_tools_Cpu64_Action" will return false due to the following conditions:
(01) 2017-11-17 07:12:38 Slp: Condition "Validate feature dependencies for package: sql_tools_Cpu64. The condition ensures that at least one of the features to be changed has its dependencies satisified." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Checking the state of all features the package depends on.
(01) 2017-11-17 07:12:38 Slp: Condition "Feature dependency condition for action: Install_sql_tools_Cpu64_Action, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:38 Slp: Condition "Feature dependency condition for action: Install_sql_tools_Cpu64_Action, the condition tests feature: SDK_FNS_sql_tools_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Condition is false because the required feature SDK_Full_sql_tools_Cpu64 failed in result Result
(01) 2017-11-17 07:12:38 Slp: Condition will fail because no feature has any satisifed dependencies.
(01) 2017-11-17 07:12:38 Slp: Attempting to pause the 32 bit ngen queue for x64
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:38 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:38 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(03) 2017-11-17 07:12:38 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(03) 2017-11-17 07:12:38 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(03) 2017-11-17 07:12:38 Slp: 
(03) 2017-11-17 07:12:38 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:38 Slp: Process returned 0
(01) 2017-11-17 07:12:38 Slp: Attempting to pause the 64 bit ngen queue
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:38 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:38 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(17) 2017-11-17 07:12:38 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(17) 2017-11-17 07:12:38 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
(17) 2017-11-17 07:12:38 Slp: 
(17) 2017-11-17 07:12:38 Slp: The .NET Runtime Optimization Service is started and paused.
(01) 2017-11-17 07:12:38 Slp: Process returned 0
(01) 2017-11-17 07:12:38 Slp: Action "Install_sql_tools_loc_Cpu64_1033_Action" will return false due to the following conditions:
(01) 2017-11-17 07:12:38 Slp: Condition "Validate feature dependencies for package: sql_tools_loc_Cpu64_1033. The condition ensures that at least one of the features to be changed has its dependencies satisified." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Checking the state of all features the package depends on.
(01) 2017-11-17 07:12:38 Slp: Condition "Feature dependency condition for action: Install_sql_tools_loc_Cpu64_1033_Action, the condition tests feature: SDK_Full_Loc_sql_tools_loc_Cpu64_1033. There are 4 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Condition is false because the required feature SDK_Full_Extensions_Loc_sql_tools_extensions_loc_Cpu64_1033 failed in result Result
(01) 2017-11-17 07:12:38 Slp: Condition "Feature dependency condition for action: Install_sql_tools_loc_Cpu64_1033_Action, the condition tests feature: SDK_FLS_sql_tools_loc_Cpu64_1033. There are 2 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:38 Slp: Condition is false because the required feature SDK_Full_Loc_sql_tools_loc_Cpu64_1033 failed in result Result
(01) 2017-11-17 07:12:38 Slp: Condition will fail because no feature has any satisifed dependencies.
(01) 2017-11-17 07:12:38 Slp: Attempting to pause the 32 bit ngen queue for x64
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
(01) 2017-11-17 07:12:38 Slp: Sco: Attempting to get registry value InstallPath
(01) 2017-11-17 07:12:38 Slp: ngen command to be used from .Net Framework Directory: C:\Windows\Microsoft.NET\Framework\v4.0.30319\
(01) 2017-11-17 07:12:38 Slp: Running: C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe queue pause
(06) 2017-11-17 07:12:38 Slp: Microsoft (R) CLR Native Image Generator - Version 4.7.2556.0
(06) 2017-11-17 07:12:38 Slp: Copyright (c) Microsoft Corporation.  All rights reserved.
..........
01) 2017-11-17 07:12:39 Slp: ------------------------------------------------------------
(01) 2017-11-17 07:12:39 Slp: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\FixSqlRegistryKey_x86.exe exit code: 0
(01) 2017-11-17 07:12:39 Slp: Completed Action: FixSqlRegistryKey, returned True
(01) 2017-11-17 07:12:39 Slp: ----------------------------------------------------------------------
(01) 2017-11-17 07:12:39 Slp: Running Action: PostMsiTimingConfigAction
(01) 2017-11-17 07:12:39 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_ConfigNonRC_postmsi" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_ConfigNonRC_postmsi, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to get feature configuration state for feature SDK_Full, version 
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to get feature flag ConfigurationState for feature SDK_Full from machine name CDM0001
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine CDM0001
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to open registry subkey 
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\140\ConfigurationState
(01) 2017-11-17 07:12:39 Slp: Sco: Attempting to get registry value SDK_Full
(01) 2017-11-17 07:12:39 Slp: Action "SLP_SDK_Dumper_install_postmsi_Cpu64" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: SLP_SDK_Dumper_install_postmsi_Cpu64, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_ConfigRC_postmsi" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_ConfigRC_postmsi, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_Startup_postmsi, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_StartupFinalize_postmsi, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Completed Action: PostMsiTimingConfigAction, returned True
(01) 2017-11-17 07:12:39 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
...........
(01) 2017-11-17 07:12:39 Slp: ----------------------------------------------------------------------
(01) 2017-11-17 07:12:39 Slp: Running Action: FinalizeTimingConfigAction
(01) 2017-11-17 07:12:39 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_Finalize_finalize" will return false due to the following conditions:
(01) 2017-11-17 07:12:39 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Install_Finalize_finalize, the condition tests feature: SDK_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
(01) 2017-11-17 07:12:39 Slp: Condition is false because the required feature SDK_Full_Extensions_sql_tools_extensions_Cpu64 failed in result Result
(01) 2017-11-17 07:12:39 Slp: Completed Action: FinalizeTimingConfigAction, returned True
(01) 2017-11-17 07:12:39 Slp: ----------------------------------------------------------------------
(01) 2017-11-17 07:12:42 Slp: 
(01) 2017-11-17 07:12:42 Slp: Error result: -2068643839
(01) 2017-11-17 07:12:42 Slp: Result facility code: 1203
(01) 2017-11-17 07:12:42 Slp: Result error code: 1
(01) 2017-11-17 07:12:42 Slp: SetupTelemetry: Closing Telemetry Session
(01) 2017-11-17 07:12:42 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:42 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
(01) 2017-11-17 07:12:42 Slp: Sco: Attempting to get registry value MachineId
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2017-11-17 07:12:43 Slp: SetupTelemetry: Not creating telemetry audit log. Value 'UserRequestedLocalAuditDirectory' doesn't exist in 'HKLM\Software\Microsoft\Microsoft SQL Server\140'
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey SQL
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value SQL2017
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL14.SQL2017\CPE
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey OLAP
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value SQL2017
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSAS14.SQL2017\CPE
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
(01) 2017-11-17 07:12:43 Slp: Sco: Attempting to open registry subkey RS
(01) 2017-11-17 07:12:43 Slp: SetupTelemetry: Telemetry has an active session with 24 events.

<o:p></o:p>

Hi,

I am working on moving a 3 TB database from single sql server 2016  to sql server always on cluster 2017. I am planning to use SQL server Log Shipping to copy the database to the two nodes and then perform an Always On Join option which works based on the testing I have done so far. 

Now I am working on rollback plan in which I reconfigure the log shipping from cluster back to single instance if rollback is needed the issue I have is that the database is 3 TB which takes around 7 hours to backup and restore. Are these any other options if anyone has used as part of rollback? I looking to decrease the downtime in rollback plan. 

Any suggestions or helpful hints?

TIA!

Good morning everyone

I installed MS SQL Server 2016 Express and Mssms 17 on a Windows server 2012 and everything works for the best.

Next i installed on Windows 10 MSSMS 17 But there is no way to be able to get the connection.

Port 1433 1434 enabled in the firewall, ping Server name OK, protocol tct Enabled with CLICONFG. exe, server-enabled Browser service.

I don't know what to do.

Can someone help me?

Marco Dell'Oca 

Hi all,

I am running a freshly installed Windows 8 Operating system (64 bit). When I run Sql Server 2014 (64 bit) Development edition, I get the following error message shownhere.

Compatibility mode is enabled in the setup.exe as shown here, still I get the above error message.

I went to windows update and tried to install any pending updates but the updates are failing as well as shownhere.

Any ideas why the error is happening and how to fix it ???

PLEASE HELP

Thanks in advance

Ram

I have SQL 2016 running in production. I changed service account through Configuration Manager from virtual account to a specific AD account created for this. However the local policy 4 permissions (Log on as a service, Replace a process-level token, Bypass traverse checking, Adjust memory quotas for a process) did not take through SQL Configuration Manager, then I added them manually, but will check if GPO will need to be changed or not. Regardless, my question is not related to these 4 (Log on as a service, Replace a process-level token, Bypass traverse checking, Adjust memory quotas for a process ) but the 3 extra for SQL Service account from

https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-windows-service-accounts-and-permissions?view=sql-server-2016#Windows

butPermission to start SQL Writer, Permission to read the Event Log service,Permission to read the Remote Procedure Call service

How do I check those last 3 are enabled for the new AD service account, since cannot find them in local policy?

Thank you,

Unable to start T-SQL Debugging.  Could not connect to computer '.'. This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

I'm using Management Studio 2008 with Sql Server 2008 Express.  I can execute queries, but I cannot debug them.  I am a member of the systemadmin role, and my server is using "local system"  as the account.  I am on a domain here at work.

I have seen http://social.msdn.microsoft.com/forums/en-US/sqlnetfx/thread/3590e35b-bb2d-45cd-be85-7698b7045be8/, but I am not doing any remote debugging.  I tried running the server under my user name, but still no luck.  I also have my firewall disabled (even though I did enable it and open up the correct ports just-in-case).

It use to work before I uninstalled and re-installed SQLEXPRESS.  What could be the issue?  I've searched everywhere, and so far everything says I should do what I've already tried.  I did have a password change, but changing it several times has not had any effect.

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

When I try to debug queries on the main 2005 sql server, I get:  Cannot execute script.  Additional Information:  Unable to start the Transact-SQL Debugger.  The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).

Moot issue, as I know the reason why this doesn't work.  But queries once-again execute here, but cannot be debugged.

Hi,

I'm running assessments for SQL 2017 compatibility of our codebase using the Data Migration Assistant. So far the tool only detected join & order by issues.

I've noticed that it does not seem to include Dynamic SQL in its analysis. We also have a bunch of applications that will issue their own SQL statements, which would logically fall out of the analysis scope.

What are the best practices for assessing the compatibility of that code? Is there a way to consult the rules that are used by the DMA tool to have a better idea what to look for?

Thanks!

I have ServerA using AD service account. I need to TSQL query database on ServerB, my AD user does not have permissions to Server B database. I have an AD proxy Contoso\ProxyAccount which is setup with proper permissions to query Server B database (if i run SSMS on Server A as proxy account I can query data from Server B). Can I setup a linked server from ServerA using this proxy account in order to run SSMS queries from server B? or is there other way? I do not want to use RunAs or Credential Manager and would prefer to use SQL tools for this.

Thank you,

Hi

We have configured Windows Failover Cluster with Windows 2016 VMs. All the disks for SQL DBs and logs will configured with in CSVs (the VMs are placed with HV 2012 R2 clustered hosts). With earlier / previous SQL installation we kept DBs & Log folders with disks partitioned with 64 KB. We are looking for a clarification for the CSVs as well disks within the VMs to be formatted, whether it should be the default 4K or 64 K? 

Thanks in advance

LMS

I've downloaded and installed DB2OLEDBV6_x64.msi on my Win 10 machine and started up SSMS 2017 (14.0.17177.0), wanting to do a linked server using the OLE DB for DB2 provider. However, that option does not appear in the drop-down. I tried the x86 install package but can't because I'm on a x64 machine/OS.

What am I doing wrong?