Hi,

Anyone can help me with this...

My company want to upgrade to SQL 2017, but don't want to upgrade the so (Windows Server 2008 r2) to reduce costs

For what I read, its not possíble.

Best regards

Joel

Thank you in Advance.

Hi,

I have a SQL server standard edition 2014 which was installed years back, i am going to uninstall and install it again due to some reason, i wanted to make sure while i will install it whether i need to have license key which i do not have since i recently joined to this organization, i asked windows team to provide license keys and they replied its a core based product and it does not require license key to install, earlier they said its a server + CAL license but now saying its core based.

my query is, if it is core based license and taken for without software assurance, and if i install it again by dowloading sql sererv 2014 installation setup will it require license key?

another question is how can i make sure what kind of license is it? 

SQL Server DBA

Not sure if I chose the right category and forum but here is my issue.

Security Update for SQL Server 2017 RTM GDR (KB4505224) - Error 0x80070643

The above is my main issue

I have troubleshooted this for two hours running windows update troubleshooter which said it fixed 3 issues and then I tried the update again and it still failed.

I tried to download the update from the microsoft windows update catalog via internet.

I tried to download a FixMissing MSI .zip file from git hub.

The below error is what I get when I ran the install application file for the KB 4505224

I have saved the error message but this site won't let me add the picture because of Body text cannot contain images or links until we are able to verify your account.

What is the best way to work around this error or fix this issue?

I thought of deleting the software distribution or backing it up and renaming it. It did not allow me to do this.

Thank you for any information you can provide 

Hi,

I set up a new cluster the other day, after doing two others successfully. This particular cluster on windows 2012 R2 is a SQL 2014 installation that has been patched to SP2 CU10. The cluster also hosts 9 other instances and a file share we use for backups for all the instances. 

It will not come online and has the error - "Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available."

I verified that dependencies were set up like the other clustered instance on this cluster, took the IP & Network name offline and then tried to ping it - no response. I put the IP/NetName online and was able to ping it. I changed the IP to a new IP provided by my network team and also known to be available. I have read through several similar threads here that mention validating registry entries and looked at those entries. I've tried bringing it up on both nodes.  The same error has occurred after all these steps.

System Log:

The SQL Server (INST10) service terminated with the following service-specific error: 
Access is denied.

SQL Log:

2018-07-05 11:41:11.59 spid16s     Could not find any IP address that this SQL Server instance depends upon.  Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available.  Error code: 0x5.
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17826, Severity: 18, State: 3.
2018-07-05 11:41:11.59 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2018-07-05 11:41:11.59 spid16s     Error: 17120, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Thanks for your review and suggestions.

Sam

Hi,

I have a requirement to downgrade SQL server 2014SP3 to SQL Server SP2. please guide me how to accomplish this task.

Note: SQL Server installed on cluster mode (2 Nodes) and from SQL ServerSP3 media.

Regards

I am trying to install SQL 2019 Preview on RHEL 7.6 .  When configuring mssql , it failed with following errors:

Error: 26024, Severity: 16, State: 1.

2019-01-25 11:44:06.39 spid23s     Server failed to listen on 'any' <ipv6> 1433. Error: 0x2742. To proceed, notify your system administrator.

2019-01-25 11:44:06.39 spid23s     Error: 17182, Severity: 16, State: 1.

2019-01-25 11:44:06.39 spid23s     TDSSNIClient initialization failed with error 0x2742, status code 0xa. Reason: Unable to initialize the TCP/IP listener. A socket operation encountered a dead network.

2019-01-25 11:44:06.39 spid23s     Error: 17182, Severity: 16, State: 1.

2019-01-25 11:44:06.39 spid23s     TDSSNIClient initialization failed with error 0x2742, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. A socket operation encountered a dead network.

2019-01-25 11:44:06.40 spid23s     Error: 17826, Severity: 18, State: 3.

2019-01-25 11:44:06.40 spid23s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2019-01-25 11:44:06.40 spid23s     Error: 17120, Severity: 16, State: 1.

2019-01-25 11:44:06.40 spid23s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

S.Prema

Hi there,

is this something related to the SSMS 18.0 edition installation?

I was using the CTP 5.0 for SSMS 18.0 and yesterday I installed 18.3.1

Thanks for your comments

Hello There,

When I sun this simple command 

EXEC master..xp_cmdshell 'BCP PDF13.dbo.TextFileRaw out D:\projects\dddd.txt -E -T -c'

I get  this error message 
output
------------------------------------------------------------------------------------------------------------------------------------------Warning: Ignoring 'E' flag when copying out. Password: CTLIB Message: - L1/O1/S1/N138/1/0: : user api layer: external error: A data length of 255 exceeds the maximum length allowed for password data. Setting connection properties failed. NULL (6 rows affected)
Looks like I have Installed a set of Sybase drivers and it changed the environment variable to point to Sybase's BCP and not SQL Server's BCP. -Came to know after some research but were to change the Environment variable back to point to SQL Server, I am not sure

Please advice

Thanks

Senthil

I'm getting the above error when trying to install a new instance of SQL Server 2017 developer edition. I've read that this can be caused by the installation trying to install an earlier version of the c++ distributable when visual studio 2017 is installed. So I've tried uninstalling visual studio, repairing then uninstalling the visual C++ redistributable (both) and running the installation under the windows administrator account, but not getting any luck. Are there any other ideas on what might work?

Hello,

My Company has bought license for SQL 2017 standard version but  it turned out it is not compatible with some stuff, we need to downgrade to 2012.  Is there a way to install 2012 Standard Edition? I can see only Express and Evaluation version available.

Thanks in advance!

I have problem installing sql svr 2014 express on win server 2008 r2 64 bits

error:

Windows Installer error message: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x8007054F.

I'm in the process of documenting SQL Product keys for SQL installed.  The people who installed it either has left the company, didn't track, or lost it/delete it.

I tried/review several methods

1. Grabbing it from the install files (https://sqlserver-help.com/2014/06/05/help-how-to-get-product-key-for-sql-server/)
2. Looking in the Installation Center, if still available (https://www.faceofit.com/how-to-find-sql-server-product-key/)
3. A powershell for SQL 2005-2014 (https://gallery.technet.microsoft.com/scriptcenter/Get-SQL-Server-Product-4b5bf4f8)
4. Updated powershell for SQL 2005-2017 (https://gist.github.com/mtrimarchi/f56e3865bad8c4578def6d2c5586a1e6)
   
   The first 3 options has help some of the servers.  But when I'm working with SQL 16 or 17 and the option 1,2,3 don't applied.
   
   Using option 4, the script will provide a product key, but it is not correct.    At first i though they wrote the wrong product key, is the reason for the mismatch product key (SQL Stand 2016). The person who install had the product key, but the script gave another product key.   Then another task, i did a fresh install of SQL Ent. 2017 with a provided product key.  It installed, but then ran option 4 powershell (just to test it), it came back with another Product key.  I confirm the two keys provided in the Update powershell were invalid.
   
   I assume the updated powershell script for SQL 2016 & 20117 is wrong??  Is there a correct powershell for finding Product key for SQL 2016 and 2017?  OR what other method can i get this information if there is no installation file and it is not written down.
   
   On a side note, Not sure were these brought with Microsoft Agreement Purchases, which say no product key needed, but during installation it automatically put a product key.  So if we brought 3 licenses, do we just use the same product key 3 times or should there be 3 product key?

Installed developer edition of SQL server on Linux. When choosing edition, option 1 is "Evaluation (free, no production use rights, 180-day limit)" and option 2 is "Developer (free, no production use rights)" (there are 6 more options which don't matter here). I chose 2, but at the end of installation got the following message:

"This is an evaluation version. There are [105] days left in the evaluation period"

I wonder why? Given that the only option that mention limits is #1 I wasn't expecting this. And I don't remember running into this issue ever before with the developer edition on Windows.

I have recently setup dev, qa, prod DataHub sql instances using 2019 rc1 developer edition in anticipation of the GA release, which occurred today Nov. 4

My PID is correct and the License Terms explicitly state MICROSOFT SQL SERVER 2019 ENTERPRISE CORE

The wizard completes successfully but SELECT @@VERSION still shows 

Microsoft SQL Server 2019 (RC1) - 15.0.1900.25 (X64)   Aug 16 2019 14:20:53   Copyright (C) 2019 Microsoft Corporation  Developer Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor) 

Is it not possible to do an edition upgrade from the release candidate to the ga?

Any insight would be helpful. Really hoping to not have to rebuild.

Hello,

We would like to go from SQL Server version 2012 to 2017, but need to know , how big the impact is.

Like the applications build with Visual Studio...which code will fail.

So, I need a nice document that simply shows which objects will be lost or are changed.

Is there such a document ? Or can I make one myself ?

Greetings,

Rob 

Hello,

   I am trying to install SQL Server 2019 on my laptop.  We have multiple versions of SQL Server on the laptops due to clients having different versions of SQL Server that we are working with.  I am trying to just install the Database Engine Services and it fails to install.  The log is very vague as to what failed, and how we can go about fixing it so that SQL Server 2019 will install along side other versions of SQL Server.

Here is the output of the log:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068643839
  Start time:                    2019-11-05 08:59:36
  End time:                      2019-11-05 09:01:48
  Requested action:              Install

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


Machine Properties:
  Machine name:                  MMASTRO-PC
  Machine processor count:       12
  OS version:                    Microsoft Windows 10 Pro (10.0.18362)
  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 2008      SQL08                MSSQL10.SQL08                  Database Engine Services                 1033                 Standard Edition     10.0.1600.22    No         Yes       
  SQL Server 2008      SQL08                MSSQL10.SQL08                  SQL Server Replication                   1033                 Standard Edition     10.0.1600.22    No         Yes       
  SQL Server 2008      SQL08                MSSQL10.SQL08                  Full-Text and Semantic Extractions for Search 1033                 Standard Edition     10.0.1600.22    No         Yes       
  SQL Server 2008 R2   SQL08R2              MSSQL10_50.SQL08R2             Database Engine Services                 1033                 Enterprise Edition   10.50.1600.1    No         Yes       
  SQL Server 2008 R2   SQL08R2              MSSQL10_50.SQL08R2             SQL Server Replication                   1033                 Enterprise Edition   10.50.1600.1    No         Yes       
  SQL Server 2008 R2   SQL08R2              MSSQL10_50.SQL08R2             Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   10.50.1600.1    No         Yes       
  SQL Server 2008 R2                                                       Client Tools Connectivity                1033                                      10.50.1600.1    No         Yes       
  SQL Server 2008 R2                                                       Client Tools Backwards Compatibility     1033                                      10.50.1600.1    No         Yes       
  SQL Server 2008 R2                                                       Integration Services                     1033                 Enterprise Edition   10.50.1600.1    No         Yes       
  SQL Server 2012      SQL12                MSSQL11.SQL12                  Database Engine Services                 1033                 Enterprise Edition   11.2.5388.0     No         Yes       
  SQL Server 2012      SQL12                MSSQL11.SQL12                  SQL Server Replication                   1033                 Enterprise Edition   11.2.5388.0     No         Yes       
  SQL Server 2012      SQL12                MSSQL11.SQL12                  Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   11.2.5388.0     No         Yes       
  SQL Server 2012      SQL12                MSSQL11.SQL12                  Data Quality Services                    1033                 Enterprise Edition   11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Client Tools Connectivity                1033                                      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Client Tools Backwards Compatibility     1033                                      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Data Quality Client                      1033                 Enterprise Edition   11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Integration Services                     1033                 Enterprise Edition   11.2.5388.0     No         Yes       
  SQL Server 2012                                                          Master Data Services                     1033                 Enterprise Edition   11.2.5058.0     No         Yes       
  SQL Server 2014      SQL14                MSSQL12.SQL14                  Database Engine Services                 1033                 Enterprise Edition   12.1.4237.0     No         Yes       
  SQL Server 2014      SQL14                MSSQL12.SQL14                  SQL Server Replication                   1033                 Enterprise Edition   12.1.4237.0     No         Yes       
  SQL Server 2014      SQL14                MSSQL12.SQL14                  Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   12.0.2000.8     No         Yes       
  SQL Server 2014      SQL14                MSSQL12.SQL14                  Data Quality Services                    1033                 Enterprise Edition   12.1.4237.0     No         Yes       
  SQL Server 2014                                                          Client Tools Connectivity                1033                                      12.1.4237.0     No         Yes       
  SQL Server 2014                                                          Client Tools Backwards Compatibility     1033                                      12.1.4237.0     No         Yes       
  SQL Server 2014                                                          Data Quality Client                      1033                 Enterprise Edition   12.1.4237.0     No         Yes       
  SQL Server 2014                                                          Integration Services                     1033                 Enterprise Edition   12.1.4237.0     No         Yes       
  SQL Server 2014                                                          Master Data Services                     1033                 Enterprise Edition   12.1.4100.1     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  Database Engine Services                 1033                 Enterprise Edition   13.0.1742.0     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  SQL Server Replication                   1033                 Enterprise Edition   13.0.1742.0     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   13.0.1601.5     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  Data Quality Services                    1033                 Enterprise Edition   13.0.1601.5     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  Machine Learning Services and Language Extensions 1033                 Enterprise Edition   13.0.1742.0     No         Yes       
  SQL Server 2016      SQL16                MSSQL13.SQL16                  R                                        1033                 Enterprise Edition   13.0.1742.0     No         Yes       
  SQL Server 2016                                                          Client Tools Connectivity                1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Client Tools Backwards Compatibility     1033                                      13.0.14500.10   No         Yes       
  SQL Server 2016                                                          Data Quality Client                      1033                 Enterprise Edition   13.0.1601.5     No         Yes       
  SQL Server 2016                                                          Integration Services                     1033                 Enterprise Edition   13.0.1601.5     No         Yes       
  SQL Server 2016                                                          LocalDB                                  1033                 Express Edition      13.1.4001.0     No         Yes       
  SQL Server 2016                                                          Master Data Services                     1033                 Enterprise Edition   13.0.1742.0     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  Database Engine Services                 1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  SQL Server Replication                   1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  Data Quality Services                    1033                 Enterprise Edition   14.0.1000.169   No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  Polybase                                 1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  Machine Learning Services and Language Extensions 1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  AdvancedAnalytics\sql_inst_mr            1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSSQL14.SQL17                  AdvancedAnalytics\sql_inst_mpy           1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017      SQL17                MSAS14.SQL17                   Analysis Services                        1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017                                                          Client Tools Connectivity                1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Client Tools Backwards Compatibility     1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Data Quality Client                      1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017                                                          Integration Services                     1033                 Enterprise Edition   14.0.2027.2     No         Yes       
  SQL Server 2017                                                          Master Data Services                     1033                 Enterprise Edition   14.0.2027.2     No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2019 
  ProductName:                   SQL Server 2019
  Type:                          RTM
  Version:                       15
  SPLevel:                       0
  Installation location:         E:\x64\setup\
  Installation edition:          Enterprise

Product Update Status:
  None discovered.

Notice: A paid SQL Server edition product key has been provided for the current action - Enterprise. Please ensure you are entitled to this SQL Server edition with proper licensing in place for the product key (edition) supplied.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLAgent$SQL19
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  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:         Automatic
  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\150\Setup Bootstrap\Log\20191105_085936\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  IACKNOWLEDGEENTCALLIMITS:      false
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    SQL19
  INSTANCENAME:                  SQL19
  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:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLJAVADIR:                    <empty>
  SQLMAXDOP:                     12
  SQLMAXMEMORY:                  2147483647
  SQLMINMEMORY:                  0
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQL19
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           STILWELL\mmastro
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQL19
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            8
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPAIDEDITIONNOTICE:     false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  USESQLRECOMMENDEDMEMORYLIMITS: false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20191105_085936\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  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.

  Feature:                       SQL Client Connectivity SDK
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.

Rules with failures or warnings:

Global rules:
Warning    IsFirewallEnabled                The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at https://go.microsoft.com/fwlink/?linkid=2094702 for information about ports to open for each feature.

Rules report file:               C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20191105_085936\SystemConfigurationCheck_Report.htm

Michael R. Mastro II

Since SQL 2019 Standard now has TDE built in, what are the gotchas if any with migrating from 2012 Enterprise to 2019 Standard.  I had planned to install a new instance of SQL and after scripting out the users and service accounts detach the DB's from 2012 and attach to 2019.

Are there gotcha's that I need to be aware of or should this upgrade go as smooth as it seems?

Thanks!

I have  sql2k16, SP2, CU10. Default instance and 1 named instance. SQLAgent runs fine with the default instance but never can start in the named instance.

I red/followed almost all threads about this subject, no way, as soon it is started, 50 seonds later it stops. Here is the output from SQLAGENT.OUT (I tried different logins domain and locals all with sysadmin privilges, tried also NT SERVICE\SQLAgent$SC2K12, activated named pipes, remote access is allowed, disabled/renabled/ DisableAgentXPs.........)

2019-11-05 18:24:29 - ? [100] Microsoft SQLServerAgent version 13.0.5492.2 (X64 unicode retail build) : Process ID 2676
2019-11-05 18:24:29 - ? [495] The SQL Server Agent startup service account is NT SERVICE\SQLAgent$SC2K12.
2019-11-05 18:24:59 - ! [150] SQL Server does not accept the connection (error: 67). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start.
2019-11-05 18:24:59 - ! [000] Unable to connect to server 'SQL2K12/SC2K12'; SQLServerAgent cannot start
2019-11-05 18:25:05 - ! [298] SQLServer Error: 67, Named Pipes Provider: Could not open a connection to SQL Server [67]. [SQLSTATE 08001]
2019-11-05 18:25:05 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00]
2019-11-05 18:25:05 - ! [298] SQLServer Error: 67, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
2019-11-05 18:25:05 - ! [382] Logon to server 'SQL2K12/SC2K12' failed (DisableAgentXPs)
2019-11-05 18:25:05 - ? [098] SQLServerAgent terminated (normally)