none
KB3207512 Failing To Install on Azure VM SS 2016 SP1 Win Svr 2016 Image

    Question

  • On Friday, 1/20, I created an Azure VM from the image 
    SQL Server 2016 SP1 Enterprise on Windows Server 2016

    On Monday, 1/23, Windows Updates downloaded and tried to install the following
    Important Update for SQL Server 2016 SP1 Reporting Services (KB3207512)
    but it failed (Error 0x80070643).  I hit the "retry" and it kept failing.  I then shut down all SQL Server services and tried again, no luck, it failed.

    I then tried to manually download the KB,  SQLServer2016-KB3207512-x64.exe.  This also failed but provided more details on the error.  The link at the bottom of the message does not go anywhere useful.  The message Details:

    Action required:
    Use the following information to resolve the error, and then try the setup process again.

    Feature failure reason:
    An error occurred for a dependency of the feature causing the setup process for the feature to fail.

    Error details:
    Error installing SQL Server Common Files
    The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
    Error code: 1642
    Log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170124_133911\MSSQLSERVER\sql_common_core_Cpu64_1.log
    Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4199.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642 to get help on troubleshooting.

    JD

    Tuesday, January 24, 2017 8:36 PM

All replies

  • Hello,

    Share with us the result of the following query:

    SELECT @@version



    Thank you in advance.



    Regards,

    Alberto Morillo
    SQLCoffee.com

    Tuesday, January 24, 2017 9:05 PM
    Moderator
  • Microsoft SQL Server 2016 (SP1-GDR) (KB3207512) - 13.0.4199.0 (X64)   Nov 18 2016 15:56:54   Copyright (c) Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Datacenter 6.3 <X64> (Build 14393: ) (Hypervisor) 

    Here is also a section from the Summary file.

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Database Engine Services                 1033                 Enterprise Edition: Core-based Licensing 13.1.4199.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            SQL Server Replication                   1033                 Enterprise Edition: Core-based Licensing 13.1.4199.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            Data Quality Services                    1033                 Enterprise Edition: Core-based Licensing 13.0.1601.5     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            R Services (In-Database)                 1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSSQL13.MSSQLSERVER            sql_inst_mr                              1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSAS13.MSSQLSERVER             Analysis Services                        1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016      MSSQLSERVER          MSRS13.MSSQLSERVER             Reporting Services - Native              1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016                                                          SSMS                                     1033                                      13.0.16100.1    No         Yes       
      SQL Server 2016                                                          Client Tools Connectivity                1033                                      13.0.14500.10   No         Yes       
      SQL Server 2016                                                          Client Tools Backwards Compatibility     1033                                      13.0.14500.10   No         Yes       
      SQL Server 2016                                                          Client Tools SDK                         1033                                      13.0.14500.10   No         Yes       
      SQL Server 2016                                                          Data Quality Client                      1033                 Enterprise Edition: Core-based Licensing 13.0.1601.5     No         Yes       
      SQL Server 2016                                                          Integration Services                     1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       
      SQL Server 2016                                                          LocalDB                                  1033                 Express Edition      13.1.4199.0     No         Yes       
      SQL Server 2016                                                          Master Data Services                     1033                 Enterprise Edition: Core-based Licensing 13.1.4001.0     No         Yes       


    JD


    • Edited by NetDude Tuesday, January 24, 2017 9:18 PM Added log snippet
    Tuesday, January 24, 2017 9:14 PM
  • Hello,

    The KB3207512 should upgrade the build of the SQL Server instance to 13.0.4199.0 but your SQL Server instance is already in that build, that means the update is already applied. There is not need to install it again.

    What you can do now is installing the latest cumulative update (CU1), released last January 18.



    Hope this helps.



    Regards,

    Alberto Morillo
    SQLCoffee.com

    Tuesday, January 24, 2017 9:28 PM
    Moderator
  • Ok, I will give that a try now.

    Wonder why Windows Update keeps trying to install it then.  Also to note, not all modules in the post above are version 13.0.4199.0, most notably SSRS, which is what the Windows Update is trying to update.


    JD

    Tuesday, January 24, 2017 9:39 PM
  • Hello,

    Just hide the update using below instructions.

    https://www.tenforums.com/tutorials/8280-windows-updates-hide-show-windows-10-a.html


    Download and apply CU1 from below URL:

    https://support.microsoft.com/en-us/help/3208177/cumulative-update-1-for-sql-server-2016-sp1


    If the update still keeps trying to install use the following tool:

    https://support.microsoft.com/en-us/instantanswers/512a5183-ffab-40c5-8a68-021e32467565/windows-update-troubleshooter



    Hope this helps.



    Regards,

    Alberto Morillo
    SQLCoffee.com


    Tuesday, January 24, 2017 9:49 PM
    Moderator
  • Unfortunately things have gotten worse.  The install of "Cumulative Update 1 for SQL Server 2016 SP1" failed on many components.

    === Verbose logging started: 1/24/2017  15:48:04  Build type: SHIP UNICODE 5.00.10011.00  Calling process: G:\e0c063e199180f8dbd\x64\ScenarioEngine.exe ===
    MSI (c) (C4:BC) [15:48:04:254]: Resetting cached policy values
    MSI (c) (C4:BC) [15:48:04:254]: Machine policy value 'Debug' is 0
    MSI (c) (C4:BC) [15:48:04:254]: ******* RunEngine:
               ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
               ******* Action: 
               ******* CommandLine: **********
    MSI (c) (C4:BC) [15:48:04:254]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (C4:BC) [15:48:04:254]: Grabbed execution mutex.
    MSI (c) (C4:BC) [15:48:04:254]: Cloaking enabled.
    MSI (c) (C4:BC) [15:48:04:254]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (C4:BC) [15:48:04:254]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (90:60) [15:48:04:254]: Running installation inside multi-package transaction {57846DA8-8B5D-4466-B850-E8CDFC94046C}
    MSI (s) (90:60) [15:48:04:254]: Grabbed execution mutex.
    MSI (s) (90:A4) [15:48:04:254]: Resetting cached policy values
    MSI (s) (90:A4) [15:48:04:254]: Machine policy value 'Debug' is 0
    MSI (s) (90:A4) [15:48:04:254]: ******* RunEngine:
               ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
               ******* Action: 
               ******* CommandLine: **********
    MSI (s) (90:A4) [15:48:04:254]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (90:A4) [15:48:04:254]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038 
    MSI (s) (90:A4) [15:48:04:254]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (90:A4) [15:48:04:254]: MSCOREE not loaded loading copy from system32
    MSI (s) (90:A4) [15:48:04:269]: End dialog not enabled
    MSI (s) (90:A4) [15:48:04:269]: Original package ==> C:\Windows\Installer\8acbb.msi
    MSI (s) (90:A4) [15:48:04:269]: Package we're running from ==> C:\Windows\Installer\8acbb.msi
    MSI (s) (90:A4) [15:48:04:269]: APPCOMPAT: Uninstall Flags override found.
    MSI (s) (90:A4) [15:48:04:269]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (s) (90:A4) [15:48:04:269]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (s) (90:A4) [15:48:04:269]: APPCOMPAT: looking for appcompat database entry with ProductCode '{57846DA8-8B5D-4466-B850-E8CDFC94046C}'.
    MSI (s) (90:A4) [15:48:04:269]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (90:A4) [15:48:04:269]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2 
    MSI (s) (90:A4) [15:48:04:269]: File will have security applied from OpCode.
    MSI (s) (90:A4) [15:48:04:269]: Original patch ==> G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp
    MSI (s) (90:A4) [15:48:04:269]: Patch we're running from ==> C:\Windows\Installer\80cb73.msp
    MSI (s) (90:A4) [15:48:04:269]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp' against software restriction policy
    MSI (s) (90:A4) [15:48:04:269]: SOFTWARE RESTRICTION POLICY: G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp has a digital signature
    MSI (s) (90:A4) [15:48:04:285]: SOFTWARE RESTRICTION POLICY: G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (90:A4) [15:48:04:285]: SequencePatches starts. Product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C}, Product version: 13.0.1601.5, Upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}, Product language 1033
    MSI (s) (90:A4) [15:48:04:285]: PATCH SEQUENCER: verifying the applicability of QFE patch G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp against product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C}, product version: 13.0.1601.5, product language 1033 and upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}
    MSI (s) (90:A4) [15:48:04:285]: PATCH SEQUENCER: QFE patch G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp is not applicable.
    MSI (s) (90:A4) [15:48:04:285]: SequencePatches returns success.
    MSI (s) (90:A4) [15:48:04:285]: Final Patch Application Order:
    MSI (s) (90:A4) [15:48:04:285]: Other Patches:
    MSI (s) (90:A4) [15:48:04:285]: Unknown\Absent: {21B7AAB3-2988-46A7-8B23-0E5C330BB30E} - G:\e0c063e199180f8dbd\x64\setup\sql_common_core_msi\sql_common_core.msp
    MSI (s) (90:A4) [15:48:04:285]: Product: SQL Server 2016 Common Files - Update '{21B7AAB3-2988-46A7-8B23-0E5C330BB30E}' could not be installed. Error code 1642. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170124_154517\MSSQLSERVER\sql_common_core_Cpu64_1.log.

    MSI (s) (90:A4) [15:48:04:285]: Windows Installer installed an update. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: {21B7AAB3-2988-46A7-8B23-0E5C330BB30E}. Installation success or error status: 1642.

    MSI (s) (90:A4) [15:48:04:285]: Note: 1: 1708 
    MSI (s) (90:A4) [15:48:04:285]: Product: SQL Server 2016 Common Files -- Installation failed.

    MSI (s) (90:A4) [15:48:04:285]: Windows Installer installed the product. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1642.

    MSI (s) (90:A4) [15:48:04:285]: Attempting to delete file C:\Windows\Installer\80cb73.msp
    MSI (s) (90:A4) [15:48:04:285]: MainEngineThread is returning 1642
    MSI (s) (90:60) [15:48:04:285]: No System Restore sequence number for this installation.
    The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
    C:\Windows\Installer\8acbb.msi
    MSI (s) (90:60) [15:48:04:285]: User policy value 'DisableRollback' is 0
    MSI (s) (90:60) [15:48:04:285]: Machine policy value 'DisableRollback' is 0
    MSI (s) (90:60) [15:48:04:285]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (90:60) [15:48:04:285]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (90:60) [15:48:04:285]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (90:60) [15:48:04:285]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (C4:BC) [15:48:04:285]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (C4:BC) [15:48:04:301]: MainEngineThread is returning 1642
    === Verbose logging stopped: 1/24/2017  15:48:04 ===


    JD

    Tuesday, January 24, 2017 9:59 PM
  • Hello,

    Could you please run the FindSQLInstalls.vbs script? I suspect there are some missing cache files that are causing this error.

    https://support.microsoft.com/en-us/help/969052/how-to-restore-the-missing-windows-installer-cache-files-and-resolve-problems-that-occur-during-a-sql-server-update

      

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Tuesday, January 24, 2017 10:13 PM
    Moderator
  • Ok, so I started by running the Repair via SQL Server from the Installation Center.  This ran without errors.

    I then tried to run the CU1 and had more errors than before.

    I reran the Repair, then ran the script.  It came back with 6 issues which appear below.  I am unable to copy them because the source folder does not exist under Package Cache.

         Copy "C:\ProgramData\Package Cache\{6FD34448-A129-4D34-B0CD-04104B1ECCFB}v13.0.15000.23\x64\smo.msi" C:\Windows\Installer\27b85.msi
         Copy "C:\ProgramData\Package Cache\{781C477A-4685-4155-82FF-15CAED269280}v13.0.15000.23\x64\TSqlLanguageService.msi" C:\Windows\Installer\27b48.msi
         Copy "C:\ProgramData\Package Cache\{61F9A46C-70EB-4CB5-8FDA-3169A5DEF49B}v13.0.15000.23\x64\conn_info.msi" C:\Windows\Installer\27b5c.msi
         Copy "C:\ProgramData\Package Cache\{6ECB5D2E-AF2E-4E1B-A311-3CD800DF2A5F}v13.0.1601.5\x86\ReportViewer.msi" C:\Windows\Installer\27b2c.msi
         Copy "C:\ProgramData\Package Cache\{22A14E6E-87B5-4142-AFEB-1453C2C9D4E8}v13.0.15000.23\x64\smo_loc.msi" C:\Windows\Installer\27b9f.msi
         Copy "C:\ProgramData\Package Cache\{76B813BF-D08D-43BB-AFF3-78110792E015}v13.0.15000.23\x64\conn_info_loc.msi" C:\Windows\Installer\27b6b.msi

    What do I do now?  BTW, this was a standard azure image that I did not change anything on, so its a little crazy I find myself in this position as a result of the windows update process.  It has put the brakes on a new vm server going live.


    JD

    Wednesday, January 25, 2017 3:50 PM
  • Hello,

    My suggestion is to run the VBScript on the following support article, place the last service pack/update and the original media on the places where the report created by VBScript is trying to find them, and then the script will recreate those MSI for you.

    https://support.microsoft.com/en-us/help/969052/how-to-restore-the-missing-windows-installer-cache-files-and-resolve-problems-that-occur-during-a-sql-server-update


     

    Hope this helps.



    Regards,

    Alberto Morillo
    SQLCoffee.com

    Wednesday, January 25, 2017 6:29 PM
    Moderator
  • Since the intent of this server was to be a database server, I decided to grab a new image and start fresh.  I am not sure why things became corrupted, but in any event, I am back on track.

    Thank you for your efforts in pointing me to some alternative things to try.  I wish they had panned out, but its time to move on.


    JD

    Wednesday, January 25, 2017 7:29 PM
  • Hello,

    I am glad you were on a position to decide a fresh start instead of troubleshooting those missing MSI cache files.

    Thank you for visiting MSDN forums!

    Have a great day.



    Regards,

    Alberto Morillo
    SQLCoffee.com

    Wednesday, January 25, 2017 8:24 PM
    Moderator
  • I'm having the same issues with the Azure images of Windows Server 2016 with SQL 2016 SP1 - unable to install CU1.

    This Image is crap.
    Happening on all our 4 VMs with that image (Test, PrePROD, UAT, DR).

    I'll try the VB Script thingy...

    Monday, January 30, 2017 12:33 PM
  • Same issue here. Anyone managed to fix it?
    Sunday, February 12, 2017 8:27 AM
  • None of these solutions worked for us.

    What did work however, was to download the original ISO from MSDN (and not use the one on the VM's C: drive). Then perform a repair of SQL using the downloaded ISO. The first time around if partially repaired. We rebooted and repaired again.

    This time around the repair was able to complete without any issues.

    After being able to repair, installing the CU1 worked just fine.

    I'll never trust an Azure "Official SQL" image after this debacle. I'd just rather build it all myself and know it's done right. What's worse is that the support from MS in this forum is so quiet, that even crickets feel awkward.

    Hope it helps you @alanplum.

    Edit: We repaired using ISO that had "SQL 2016 with SP1"


    • Edited by Jaans Sunday, February 12, 2017 8:44 AM additional info
    • Proposed as answer by alanplum Sunday, February 12, 2017 8:51 AM
    Sunday, February 12, 2017 8:43 AM
  • Thanks for that. I've just sorted it another way thanks to your post. Just reinstall SP1 then CU1 Seems to be a slipstreaming issue with the one on the C drive.
    • Proposed as answer by Alon.or Sunday, January 21, 2018 8:49 AM
    Sunday, February 12, 2017 8:51 AM
  • Saw this exact same issue in our production system with CU 4 - reinstalling SP1 solved the problem.  CU 1 through 4 installed without issue after that.

    Tuesday, August 29, 2017 6:38 PM
  • Same here, trying to go from SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) to CU7 SQL Server 2016 (SP1-CU7-GDR) (KB4057119) - 13.0.4466.4 (X64) was failing in a weird way with Error code 1642 as seen in picture:

    Solved it by re-applying SP1 then Cu7 installed successfully without even restarting the server.

    This was done on a High Availability Always On Cluster of 3 servers.


    • Edited by Alon.or Sunday, January 21, 2018 8:59 AM
    Sunday, January 21, 2018 8:57 AM
  • Thanks!
    Tuesday, February 20, 2018 10:54 AM
  • Thanks all, same issue here with an Azure SQL Server 2016 SP1 image.

    Installing SP2 resolved it for me.

    Sunday, June 17, 2018 12:58 PM