Forum Discussion

VinaySarangam's avatar
VinaySarangam
Icon for Microsoft rankMicrosoft
Oct 17, 2024

Error:1648: No valid sequence could be found for the set of updates" Error while Patching

Problem Description:-In General, while Performing Installation or patching failure troubleshooting we will be verifying "detail.txt" file in "setup bootstrap" Folder in the location "C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20241009_095428\MSSQLSERVER" for SQL Server 2019 version. If we did not find anything in the "detail.txt" file, we need to look in to other component logs as well. In this case we are having component logs "sql_engine_core_inst_cpu64_1.log & sql_fulltext_cpu64_1.log" as mentioned in the below screenshot: 

 

 

In One of the other component log "sql_dqc_Cpu64_1.log" we found "No valid sequence could be found for the set of updates" as mentioned below:
 

Detailed results:

Feature: Data Quality Client

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 to uninstall this feature again.

Component name: SQL Server Data Quality Client

Component error code: 1648

Component log file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20210112_003431\sql_dqc_Cpu64_1.log

Error description: No valid sequence could be found for the set of updates.

Feature: Setup Support Files

 

Applicable To:- SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017, SQL Server 2019, SQL Server 2022 & so on……..

 

Resolution Options:-

  1. Go to Run and type "c:\windows\installer" and press enter
  2. You will be redirected to Installer cache folder. In the Installer cache folder sort with the column size. You will be observing 20KB files as mentioned in the below screenshot:

    Above screenshot means that all the msi/msp files are corrupted. "Fix MSI Installer" tool or VB script to fix missing msi will not be able to resolve this issue as they check with the name whether the file containing the name is missing or not in the location. If its missing, they will report as missing otherwise no
  3. After finding the malfunctioned 20KB files we will be having two options as mentioned below:
    Option 1:-
    1. Clear/Remove/move all the files from the Installer cache folder
    2. Repair SQL Server Instance.
    Option 2:-
    1. Please download "FixMissingMSI" tool from the below link:     https://github.com/suyouquan/SQLSetupTools/releases/download/V2.2.1/FixMissingMSI_V2.2.1_For_NET45.zip
    2.     Provide SQL Server patch location as mentioned below and click scan now:
     
    3. You will be getting below screenshot where we need to pay attention to the columns "PackageName", "Cachedmsimsp", "Product Name", "CachedMsiMspVersion" :
     
    4. At this point of time we are having malfunctioned msi,msp file names and the above mentioned output from "FixMissingMSI" tool output
    5. Firstly, to start with pick one malfunctioned missing msi file and search in the "FixMissingMSI" tool. Let's say for example We searched for this file "    13a3f6f.msp" and found the file as mentioned in the below screenshot: 
     
    6. After that we need to look in to the "ProductName" column and check the KB Number. In this case the KB number we got is KB5046061.
    7. Now I need to search for the malfunctioned msp file "    13a3f6f.msp" in the  KB5046061. We will be searching with the "PackageName" of the msp file which is "sql_fulltext.msp" in media/software which we downloaded for the KB5046061
    8. Now after finding the file in the  media, We need to copy it to the installer cache folder by renaming the old malfunctioned msp with "    13a3f6f_old.msp". After copying the clean file("sql_fulltext.msp" ) from the software to installer cache folder we need to rename the file from "sql_fulltext.msp" to "13a3f6f.msp"
    9. After this we need to repeat the same procedure for all the malfunctioned 20KB files 
    10. If we did not find the KB number in the 6th step we need  to verify the "CachedMsiMspVersion" or "ProductVersion" and needs to look for the malfunctioned file in the software pertaining to that build number and follow the steps from 7 to 9
    11. After fixing all the msi/msp files from the above-mentioned steps we will be able to resolve the issue successfully
No RepliesBe the first to reply

Resources