Apr 10 2024 06:47 PM
So I've seen this error on 5 separate servers after attempting to upgrade from SQL Server 2019 (RTM-CU22-GDR) to SQL Server 2022, CU11.
The only way I could get SQL Setup to complete successfully was by first uninstalling both ODBC 17 and OLEDB driver using Add/Remove Programs (then rebooting).
Has anyone else experienced this? It seems to me this might be a setup bug. I thought maybe it was because some of the servers have multiple ODBC drivers (one from SQL 2016 and 2019), but even the servers with only ONE version of the driver (17), it still threw an error. I have attached the detailed log file (with user names and computer names obfuscated)
Feature failure reason: An error occured for a dependency of the feature causing the setup process for the feature to fail.
Error details: Error installing Microsoft ODBC Driver for SQL Server Fatal error during installation
Error code: 1603
Error details from the msodbcsql_Cpu64_1_Local.log setup log... (Attached as PDF file)
NOTE: FullText search is probably a red-herring because one of the servers did NOT have FullText Search installed. The same ODBC error is showing under Database Engine Services as well.
Detailed Steps:
1. Copied all of our setup bits to local folder on server
2. Ran setup from command line (slip-streaming CU11 update):
SETUP.EXE /Action=upgrade /PRODUCTCOVEREDBYSA /SUPPRESSPRIVACYSTATEMENTNOTICE /IACCEPTSQLSERVERLICENSETERMS /INSTANCENAME=MSSQLSERVER /UpdateEnabled=True /UpdateSource=".\Updates"
3. The pre-requisite check in the setup wizard completes successfully with no errors for either ODBC or OLEDB (as shown in the screenshot below).
4. Run setup -- which finally aborts with the error: Error installing Microsoft ODBC Driver for SQL Server Fatal error during installation
5. To "workaround" the problem, I uninstall both ODBC and OLEDB from Add/Remove Programs and then reboot the server. After that, I was able to successfully run SETUP with no errors.
Apr 11 2024 11:47 AM
Apr 12 2024 05:49 AM
Apr 12 2024 03:30 PM
@MarlonRibunal I was already running CU22-GDR for SQL 2019.
Now The one commonality -- these servers had either FullText Search, SSIS, and ONE server was enabled Distribution server (for Replication). Otherwise, all of our basic vanilla SQL Servers (only SQL Server engine installed) had no problems.
I'm not sure I'll get another chance to try to reproduce this in our environment.
Apr 12 2024 03:34 PM