The installation program encountered an error: The given keyword is not in the dictionary

Hi @佳骏 白 ,

This error is usually caused by corrupted setup files or regional settings mismatch, not necessarily cluster/CDC issues.

Please try bellow ways,

• Re-download SQL server installation media from official source
• Extract and run setup from local drive (not network/ZIP)
• Set system locale to english (united states) and restart
• Run setup as Administrator

If the issue still persists, please share 1. SQL server version 2. Exact step where error occurs 3. Setup logs (Summary.txt / Detail.txt from Setup Bootstrap\Log folder)

That will help identify the exact root cause.

Thanks,
Akhil.

The error message "The given key was not present in the dictionary" during SQL Server installation is a known generic setup/configuration failure that can occur in several SQL Server components.

From the available information, the supported resolutions in similar cases are:

1. If this occurs during a Failover Clustered Instance (FCI) installation on Windows Server 2019 in Azure
   • The issue can be caused by the Windows Server 2019 ManagementPointNetworkType cluster switch being set to Automatic, which on Azure uses a Distributed Network Name.
   • SQL Server FCI installation is not supported on a Windows cluster that has only a Distributed Network Name and no NetworkName resource, which leads to the "The given key was not present in the dictionary" error during configuration.
   • Resolution in that scenario:
     1. Delete the existing Windows failover cluster.
     2. Recreate the cluster using PowerShell and explicitly set the management point network type to singleton, for example:

                New-Cluster -Name <ClusterName> -Node <NodeList> -StaticAddress <IP> -ManagementPointNetworkType Singleton
        

     3. After the cluster is recreated with a traditional NetworkName resource, rerun the SQL Server FCI setup.
2. If this occurs in other SQL Server setup scenarios (non-FCI)
   • The same error text can appear for other installation problems. In such cases, the documented generic remediation steps are:
     1. Download the SQL Server installation media again from the original source and rerun setup, in case the media is corrupted.
     2. If setup is being run from a network share, copy the media to a local drive and run setup locally.
     3. Rename the Setup.rll file under the SQL Server setup resources folder and rerun setup:
        • Navigate to: C:\Program Files\Microsoft SQL Server\1XX\Setup Bootstrap\SQLXXX\resources\1033
        • Rename Setup.rll to Setup.rll.old.
        • Run setup again.
     4. For localized SQL Server versions, ensure the operating system regional/language settings support the SQL Server language, and avoid mixing different SQL Server language versions on the same machine.
3. If the error appears when using CDC Source in SSIS (SQL Server 2014/2016/2017)
   • The same error text is a known bug when previewing data in the CDC Source task after installing certain cumulative updates.
   • The resolution is to install the documented cumulative update for the corresponding SQL Server version:
     • SQL Server 2017: install at least Cumulative Update 15 for SQL Server 2017.
     • SQL Server 2016: install CU6 for SQL Server 2016 SP2 or CU14 for SQL Server 2016 SP1.
     • SQL Server 2014: install CU3 for SQL Server 2014 SP3.

For a Reporting Services–specific installation, the exact cause and fix depend on where in setup the error occurs (clustered vs. standalone, CDC/SSIS usage, or generic setup). The next step is to:

• Check the SQL Server setup Summary.txt and Detail.txt logs under the Setup Bootstrap\Log folder to identify whether the failure matches one of the documented scenarios above (FCI on Azure/Server 2019, generic setup failure, or CDC Source preview issue), and then apply the corresponding resolution.

References:

• Error (The given key was not present in the dictionary) and SQL Server FCI installation fails on an Azure VM in Server 2019
• SQL Server installation errors
• KB4500595 - FIX: CDC Source preview fails with "The given key was not present in the dictionary" error in SQL Server 2017
• KB4492379 - FIX: CDC source preview fails with "The given key was not present in the dictionary" in SQL Server 2014
• KB4490435 - FIX: "The given key was not present in the dictionary" occurs if you do a preview in the CDC Source in SQL Server 2016