question

VictorRGV-7897 avatar image
0 Votes"
VictorRGV-7897 asked ErlandSommarskog commented

SQL Server 2019 Upgrade Problem

I am attempting to upgrade from SQL Express 2014R2 to SQL 2019 Standard and have run into an issue :: Database Engine Services -FAILED :: SQL Client Connectivity SDK - FAILED

We have run out of room with the Database and Express ;;; Thanks in Advance

This is the Summary

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2022-05-15 07:40:46
End time: 2022-05-15 07:43:19
Requested action: Upgrade

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: SERVER
Machine processor count: 12
OS version: Microsoft Windows Server 2016 Standard (10.0.14393)
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 OMSQL MSSQL12.OMSQL Database Engine Services 1033 Express Edition 12.3.6164.21 No Yes
SQL Server 2014 SSMS 1033 Express Edition 12.3.6164.21 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: Standard

Product Update Status:
None discovered.

Notice: A paid SQL Server edition product key has been provided for the current action - Standard. 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: Upgrade
AGTDOMAINGROUP: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220515_074046\ConfigurationFile.ini
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FAILOVERCLUSTERROLLOWNERSHIP: 2
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
FTUPGRADEOPTION: Import
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTRSUNINSTALL: false
IACCEPTSQLSERVERLICENSETERMS: true
IACKNOWLEDGEENTCALLIMITS: false
INDICATEPROGRESS: false
INSTANCEID: OMSQL
INSTANCENAME: OMSQL
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
MRCACHEDIRECTORY:
PID: *
QUIET: false
QUIETSIMPLE: false
RSCATALOGSERVERINSTANCENAME: Unknown
SQLTELSVCACCT: NT Service\SQLTELEMETRY$OMSQL
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SUPPRESSPAIDEDITIONNOTICE: false
SUPPRESSPRIVACYSTATEMENTNOTICE: false
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220515_074046\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:

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


sql-server-generalsql-server-migration
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

In the folder : C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20220515_074046 there are a number of log files, all quite verbose. The most interesting one is detail.txt. Looks in this one, or upload it here.

0 Votes 0 ·
ErlandSommarskog avatar image
1 Vote"
ErlandSommarskog answered

I found this in the log:

MSI (s) (EC:04) [07:42:57:911]: Executing op: ChangeMedia(MediaVolumeLabel=SQLNCLI11,MediaPrompt=Please insert the disk: ,MediaCabinet=Redist.cab,BytesPerTick=65536,CopierType=2,ModuleFileName=1\sqlncli.msi,,,,,IsFirstPhysicalMedia=1)
MSI (s) (EC:04) [07:42:57:911]: Executing op: FileCopy(SourceName=sqlncli.h,SourceCabKey=DP_sqlncli_h_32,DestName=sqlncli.h,Attributes=0,FileSize=175473,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=807962593,HashPart2=269415791,HashPart3=-1317500142,HashPart4=-326144871,,)
MSI (s) (EC:04) [07:42:57:926]: File: C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Include\sqlncli.h; To be installed; Won't patch; No existing file
MSI (s) (EC:04) [07:42:57:926]: Source for file 'DP_sqlncli_h_32' is compressed
MSI (s) (EC:04) [07:42:57:926]: Note: 1: 2203 2: E:\sqlncli.msi 3: -2147287038
MSI (s) (EC:04) [07:42:57:926]: Source is incorrect. Unable to open or validate MSI package E:\sqlncli.msi.
MSI (s) (EC:04) [07:43:08:084]: Note: 1: 2203 2: E:\sqlncli.msi 3: -2147287038
MSI (s) (EC:04) [07:43:08:084]: Source is incorrect. Unable to open or validate MSI package E:\sqlncli.msi.
Please insert the disk:

So it seems that is looking for the msi file directly under the root of E:. Yet, in the top of the file, I see the path E:\1033_ENU_LP\x64\setup\x64\sqlncli.msi. So it seems that during the course of execution, it lost the path. Why, I have no idea.

You could try copying the MSI: file to E:. Then again, I assume that given the path that this is a DVD drive. Maybe copy the DVD to local disk and try again?

I hope you realise that I'm clutching at straws here. In the end, it may be more straightforward to install a new instance, although this will cause a problem with connecting clients. And you will need to copy logins etc from the old instance.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

VictorRGV-7897 avatar image
0 Votes"
VictorRGV-7897 answered ErlandSommarskog commented

Attached ... it's Large202023-detail.txt



detail.txt (3.0 MiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Unfortunately, I was not able to draw any conclusion. I did find a stack trace for Install_sqlncli_Cpu64_Action, which is said to return error 1602, which according to NET HELPMSG means User cancelled installation.

I am not sure why Setup would run this action, since SQL 2019 uses the newer provider MSOLEDBSQL. Anyway, do you have a log file with sqlncli in the name? Maybe there is something interesting there?

General comment: I'm by no means an expert on SQL Server setup. The log files are as I said very verbose. Sometimes when I help people with setup problems, there is something apparent that stands out. Sometimes it is just a mystery.

Am I right to assume that this originally was an instance running SQL 2008 R2 and then upgraded to SQL 2014?

0 Votes 0 ·
VictorRGV-7897 avatar image
0 Votes"
VictorRGV-7897 answered

Erland, Yes to the Upgrades :: note: that these are all Express and I now am out of space . I need to upgrade my system and cannot until the upgrade.




File attached202066-sqlncli-cpu64-1.log



sqlncli-cpu64-1.log (204.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

VictorRGV-7897 avatar image
0 Votes"
VictorRGV-7897 answered ErlandSommarskog commented

Does this help as well?

2022-05-15 07:42:21.37 Server Microsoft SQL Server 2014 (SP3-GDR) (KB4583463) - 12.0.6164.21 (X64)
Nov 1 2020 04:25:14
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 14393: )

2022-05-15 07:42:21.37 Server UTC adjustment: -5:00
2022-05-15 07:42:21.37 Server (c) Microsoft Corporation.
2022-05-15 07:42:21.37 Server All rights reserved.
2022-05-15 07:42:21.37 Server Server process ID is 6804.
2022-05-15 07:42:21.37 Server System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T340'.
2022-05-15 07:42:21.37 Server Authentication mode is MIXED.
2022-05-15 07:42:21.37 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.OMSQL\MSSQL\Log\ERRORLOG'.
2022-05-15 07:42:21.38 Server The service account is 'VISION\SERVER$'. This is an informational message; no user action is required.
2022-05-15 07:42:21.38 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.OMSQL\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.OMSQL\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.OMSQL\MSSQL\DATA\mastlog.ldf
2022-05-15 07:42:21.38 Server Command Line Startup Parameters:
-s "OMSQL"
2022-05-15 07:42:21.66 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-05-15 07:42:21.66 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-05-15 07:42:21.66 Server Detected 16101 MB of RAM. This is an informational message; no user action is required.
2022-05-15 07:42:21.66 Server Using conventional memory in the memory manager.
2022-05-15 07:42:21.80 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2022-05-15 07:42:21.93 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-05-15 07:42:21.93 Server This instance of SQL Server last reported using a process ID of 2104 at 5/15/2022 7:42:20 AM (local) 5/15/2022 12:42:20 PM (UTC). This is an informational message only; no user action is required.
2022-05-15 07:42:21.93 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-05-15 07:42:21.93 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2022-05-15 07:42:21.93 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2022-05-15 07:42:21.95 Server Software Usage Metrics is disabled.
2022-05-15 07:42:21.96 spid7s Starting up database 'master'.
2022-05-15 07:42:22.04 Server CLR version v4.0.30319 loaded.
2022-05-15 07:42:22.10 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-05-15 07:42:22.10 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2022-05-15 07:42:22.16 spid7s SQL Trace ID 1 was started by login "sa".
2022-05-15 07:42:22.16 spid7s Server name is 'SERVER\OMSQL'. This is an informational message only. No user action is required.
2022-05-15 07:42:22.16 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.
2022-05-15 07:42:22.16 spid11s Starting up database 'mssqlsystemresource'.
2022-05-15 07:42:22.16 spid20s Starting up database 'OMATESQL'.
2022-05-15 07:42:22.16 spid18s Starting up database 'msdb'.
2022-05-15 07:42:22.16 spid19s Starting up database 'DynamicFootprint'.
2022-05-15 07:42:22.17 spid15s A self-generated certificate was successfully loaded for encryption.
2022-05-15 07:42:22.17 spid15s Server is listening on [ 'any' <ipv6> 49800].
2022-05-15 07:42:22.17 spid15s Server is listening on [ 'any' <ipv4> 49800].
2022-05-15 07:42:22.17 spid15s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\OMSQL ].
2022-05-15 07:42:22.17 spid15s Server named pipe provider is ready to accept connection on [ \.\pipe\MSSQL$OMSQL\sql\query ].
2022-05-15 07:42:22.17 spid15s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2022-05-15 07:42:22.18 spid11s The resource database build version is 12.00.6164. This is an informational message only. No user action is required.
2022-05-15 07:42:22.18 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-05-15 07:42:22.18 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2022-05-15 07:42:22.18 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Server:OMSQL ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2022-05-15 07:42:22.18 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/Server:49800 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2022-05-15 07:42:22.25 spid11s Starting up database 'model'.
2022-05-15 07:42:22.40 spid11s Clearing tempdb database.
2022-05-15 07:42:23.09 spid11s Starting up database 'tempdb'.
2022-05-15 07:42:23.15 spid21s The Service Broker endpoint is in disabled or stopped state.
2022-05-15 07:42:23.15 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2022-05-15 07:42:23.17 spid21s Service Broker manager has started.
2022-05-15 07:42:23.28 spid7s Recovery is complete. This is an informational message only. No user action is required.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I see nothing alarming in the SQL Server errorlog. And the issue seems to be with SQL Native Client, so it was not really expected to find anything here.

0 Votes 0 ·
VictorRGV-7897 avatar image
0 Votes"
VictorRGV-7897 answered

Erland,

I am using an ISO which is mounted via OS. Now that that is in the log, I have noticed that I am remounting the ISO. Let me create new media and attempt this again. I'm out of time today , so it may be a day or two.

Thanks for the help so far.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

VictorRGV-7897 avatar image
1 Vote"
VictorRGV-7897 answered ErlandSommarskog commented

Erland,

Update: You were very CORRECT. I went to make a USB and noticed that a download of a flat file was available. I have plenty of drive space and 15 minutes later, I now have SQL 2019 Standard installed.

Now for testing!

AGAIN: THANKS!!!

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

That's brilliant! I'm really glad to hear that my observations helped you get the installation complete successfully!

0 Votes 0 ·