none
Cannot install CU - The baseline msi is not installed. The patch package is ignored.

    Question

  • Hi All,

    The story begins one of our SQL Server cluster didn't get update from software center, and then I found in Software Center it says "install ignored" or message like this, as other SQL server clusters get upgraded successfully, I did investigation on this cluster to see what happened.


    Firstly I checked the current version on one node of this cluster, which is on 12.0.5203.0

    The other clusters have been upgraded to 12.0.5532(KB #3194718), so I tried to manually install this CU on this cluster to keep them consistent, however I got below error:

    .....

    (01) 2017-01-30 09:28:33 Slp: Sco: File 'g:\2996ba839d9f530ebdc2\x64\setup\sql_engine_core_inst_msi\x86\sql_engine_core_inst.msp' does not exist
    (01) 2017-01-30 09:28:33 Slp: Sco: File 'g:\2996ba839d9f530ebdc2\1028_CHT_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msp' does not exist
    (01) 2017-01-30 09:28:33 Slp: Sco: File 'g:\2996ba839d9f530ebdc2\1031_DEU_LP\x64\setup\sql_engine_core_inst_loc_msi\x64\sql_engine_core_inst_loc.msp' does not exist

    ....

    (01) 2017-01-30 09:28:38 Slp: Package sql_engine_core_inst_Cpu64: - The path of cached MSI package is: C:\Windows\Installer\59b76a.msi . The RTM product version is: 12.0.2000.8
    (01) 2017-01-30 09:28:38 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 12.2.5203.0
    (01) 2017-01-30 09:28:38 Slp: Patch Id KB3194718_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.  Detail description of this patch package is: PatchId=KB3194718_sql_engine_core_inst_Cpu64 PatchVersion=12.2.5532.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=12.2.5000.0; PatchFileName=sql_engine_core_inst.msp PatchCode={83CDFF67-D679-4D22-9F54-E80213C71B68}
    (01) 2017-01-30 09:28:38 Slp: Sco: File 'g:\2996ba839d9f530ebdc2\x64\setup\sql_engine_core_inst_msi\x64\sql_engine_core_inst.msp' does not exist
    (01) 2017-01-30 09:28:38 Slp: Patch Id: KB3194718_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.  The patch package is ignored.

    ...

    (01) 2017-01-30 09:30:38 Slp: Error result: -2061893565
    (01) 2017-01-30 09:30:38 Slp: Result facility code: 1306
    (01) 2017-01-30 09:30:38 Slp: Result error code: 67
    (01) 2017-01-30 09:30:38 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2017-01-30 09:30:38 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2017-01-30 09:30:38 Slp: Sco: Attempting to get registry value CustomerFeedback

    *detailed file can be found at https://drive.google.com/open?id=0B-eTNxeeWhHfU2t2S3UtMWl4dWc

    I then checked https://technet.microsoft.com/library/security/ms16-136 to see if I missed anything:

    -------------------------------------------------------

    What are the GDR and CU update designations and how do they differ? 
    The General Distribution Release (GDR) and Cumulative Update (CU) designations correspond to the two different update servicing branches in place for SQL Server. The primary difference between the two is that CU branches cumulatively include all updates for a given baseline, while GDR branches include only cumulative critical updates for a given baseline. A baseline can be the initial RTM release or a Service Pack.

    For any given baseline, either the GDR or CU branch updates are options if you are at the baseline or have only installed a previous GDR update for that baseline. The CU branch is the only option if you have installed a previous SQL Server CU for the baseline you are on.

    -------------------------------------------------------

    My first thought if I missed a version(or software center missed a version), so I downloaded 12.0.5522(KB #3188778) and tried to install, then got this:

    A SQL Server update with a higher version has already been installed on SQL Server instance INSTANCE1, so the current SQL Server update cannot be applied. The version of the SQL Server update that is already installed is GDR 12.2.5203.0(12.2.5530.0) with a KBKB3194714 and the current SQL Server update is 12.2.5522.0 with a KBKB3188778.

    I am confused by this sentence "The version of the SQL Server update that is already installed is GDR 12.2.5203.0(12.2.5530.0) with a KBKB3194714 and the current SQL Server update is 12.2.5522.0 with a KBKB3188778."  so the version is already installed is 12.2.5203.0 or 12.2.5530.0? I believe it is 12.2.5203.0 as it is same as the @@version, if that is the case the CU should install because 12.2.5530 is higher than 12.2.5203.0!

    Monday, January 30, 2017 12:22 AM

Answers

  • thanks guys, after a detailed check.

    Found the error in instance folder:

    (01) 2017-01-30 09:30:08 SQLEngine: --SqlEngineSetupPrivate:  Validating path:G:\MSSQL12.Instance2\MSSQL\Data 
    (01) 2017-01-30 09:30:08 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Validation and scenario Validation.
    (01) 2017-01-30 09:30:08 Slp: The User Data directory in the registry is not valid. Verify DefaultData key under the instance hive points to a valid directory.

    So just need to make sure the path is correct.

    • Marked as answer by AlbertZOZ Monday, January 30, 2017 11:42 PM
    • Edited by AlbertZOZ Monday, January 30, 2017 11:43 PM add more details
    Monday, January 30, 2017 11:42 PM

All replies

  • I decided to try the latest CU which is 12.0.5538(KB #3204388), 

    but got the same error:

    ...

    (01) 2017-01-30 11:24:13 Slp: Error result: -2061893565
    (01) 2017-01-30 11:24:13 Slp: Result facility code: 1306
    (01) 2017-01-30 11:24:13 Slp: Result error code: 67
    (01) 2017-01-30 11:24:13 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2017-01-30 11:24:13 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2017-01-30 11:24:13 Slp: Sco: Attempting to get registry value CustomerFeedback

    ...

    detailed log can be found at:

    https://drive.google.com/open?id=0B-eTNxeeWhHfNEVJUFM5bXBGZFU

    Dose anyone experience the same issue? or know how to fix this issue?

    Thanks very much!

    Regards,

    Albert

    Monday, January 30, 2017 12:40 AM
  • thanks guys, after a detailed check.

    Found the error in instance folder:

    (01) 2017-01-30 09:30:08 SQLEngine: --SqlEngineSetupPrivate:  Validating path:G:\MSSQL12.Instance2\MSSQL\Data 
    (01) 2017-01-30 09:30:08 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Validation and scenario Validation.
    (01) 2017-01-30 09:30:08 Slp: The User Data directory in the registry is not valid. Verify DefaultData key under the instance hive points to a valid directory.

    So just need to make sure the path is correct.

    • Marked as answer by AlbertZOZ Monday, January 30, 2017 11:42 PM
    • Edited by AlbertZOZ Monday, January 30, 2017 11:43 PM add more details
    Monday, January 30, 2017 11:42 PM