SQL Server 2019 Upgrade Problem

Victor RGV 26 Reputation points
2022-05-15T12:54:27.597+00:00

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
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,787 questions
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
532 questions
Accepted answer
  1. Erland Sommarskog 111.1K Reputation points MVP
    2022-05-15T18:36:08.797+00:00

    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.

    1 person found this answer helpful.
    0 comments

6 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Victor RGV 26 Reputation points
    2022-05-15T23:17:18.523+00:00

    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.

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.