none
Unable to install CU 1 for SQL Server 2016 SP1 through Windows Update service.

    Question

  • Installing the CU 1 for SQL Server 2016 SP1 through the Windows Update service fails on our SQL Server 2016 SP1 instances.

    -

    The summary log reports:

    Package properties:
      Description:                   Microsoft SQL Server 2016
      ProductName:                   SQL Server 2016
      Type:                          RTM
      Version:                       13
      SPLevel:                       1
      KBArticle:                     KB3208177
      KBArticleHyperlink:            http://support.microsoft.com/?kbid=3208177
      PatchType:                     QFE
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    13.1.4411.0
      ProductVersion:                13.1.4001.0
      GDRReservedRange:              13.0.1700.0:13.0.1899.0;13.0.4200.0:13.0.4299.0

    User Input Settings:
      ACTION:                        Patch
      ALLINSTANCES:                  true
      CLUSTERPASSIVE:                false
      CONFIGURATIONFILE:            
      ENU:                           false
      HELP:                          false
      IACCEPTROPENLICENSETERMS:      true
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTANCEID:                    <empty>
      INSTANCENAME:                  <empty>
      MRCACHEDIRECTORY:             
      QUIET:                         true
      QUIETSIMPLE:                   false
      SUPPRESSPRIVACYSTATEMENTNOTICE: false
      UIMODE:                        Normal
      X86:                           false

    Exception type: Microsoft.SqlServer.Configuration.MsiExtension.PatchNoopException
        Message:
            No features were updated during the setup execution. The requested features may not be installed or features are already at a higher patch level. Please review the summary.txt logs for further details.
            The specified cumulative update could not be applied because service pack or general distribution release is already installed.
            The specified cumulative update could not be applied because service pack or general distribution release is already installed.
        HResult : 0x86430003
            FacilityCode : 1603 (643)
            ErrorCode : 3 (0003)
        Data:
          SummaryMessage =
    The specified cumulative update could not be applied because service pack or general distribution release is already installed.
    The specified cumulative update could not be applied because service pack or general distribution release is already installed.
          WatsonData = Microsoft.SqlServer.Configuration.MsiExtension.PatchNoopException@3
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
            at Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate).

    -

    However, installing the update manually on the servers by running SQLServer2016-KB3208177-x64.exe succeeds for all the SQL Server 2016 SP1 instances.

    Thanks,
    Brynjar



    Thursday, March 9, 2017 10:15 AM

Answers

  • This is no longer an issue for me since I have installed the CU 1 for SQL Server 2016 SP1 manually on all our 2016 SP1 servers.

    Microsoft has also made a new version of "SQL Server 2016 Service Pack 1 Cumulative Update (CU) 1" KB3208177 available. I have not been able to try to install it with Windows Update, so I can't verify if the new version succeeds with Windows Update.

    Cumulative Update 2 for SQL Server 2016 SP1 has also been made available now.

    Regards,
    Brynjar

    Tuesday, March 28, 2017 8:10 AM

All replies

  • Hi Brynjar,

    I tested the installation media of Windows Update and the Official Website, the Windows Update uses the same installation media with the media you downloaded from the Official Website.

    Based on my experience, this is a problem of Windows Update, please clear up your Temporary Files and Internet Cache, reboot and try again, please use the the built-in Disk Cleanup utility. Besides, you can use the Windows Update Troubleshooter from Microsoft.

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 10, 2017 6:22 AM
  • I have the same problem on two servers that are newly installed with windows 2012R2 + SQL Server Standard 2016 version.

    Sunday, March 12, 2017 7:11 AM
  • Same problem here, install from Windows Update (WSUS) failed with error 0x80070643

    No features were updated during the setup execution. The requested features may not be installed or features are already at a higher patch level. Please review the summary.txt logs for further details.

    The specified cumulative update could not be applied because service pack or general distribution release is already installed.

    • HResult : 0x86430003
    • FacilityCode : 1603 (643)
    • ErrorCode : 3 (0003)


    Monday, March 13, 2017 9:37 AM
  • Hi Teige, tried your suggestion. Unfortunately that did not work.  I also looked in the registry and confirmed my installed version is indeed 13.0.4001.0.

    Hope someone posts a solution! 

    Thank you in advance!


    RFDZ12

    Tuesday, March 14, 2017 8:14 PM
  • Hi Brynjar,

    We are currently looking into this issue and will give you an update as soon as possible.

    Thank you for your understanding and support.

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, March 15, 2017 9:13 AM
  • Same here.

    One Server could be successfully manually updated to SQL2016 SP1CU1.

    Two Servers failed both manually and Windows Update, same symptom as yours. (Installed on Windows 2012R2).

    We have stopped rolling out SP1CU1 and are hoping there will be fix soon!

    Wednesday, March 15, 2017 10:09 AM
  • Hi everyone, 

    Could you please share the C:\WINDOWS\LOGS\CBS\CBS.log to us for analysis, please share it with Onedrive.

    Best Regards,

    Teige


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, March 16, 2017 10:11 AM
  • Hi Teige,

    Here: ( https://onedrive.live.com/?authkey=%21AFFuxyAEl-GwKfc&v=TextFileEditor&id=34A9425F38071985%21640&cid=34A9425F38071985&parId=34A9425F38071985%21142 ) is the cbs log from a server at version 13.1.4001.0 where installation of CU 1 for SQL Server 2016 SP1 through the Windows Update service has failed.

    Best regards,
    Brynjar 


    Thursday, March 16, 2017 11:10 AM
  • Hi Brynjar,

    Appreciate for sharing the CBS log, some engineers are working on it. Besides, we also need the windowsupdate.log. Apologize for any inconvenient. 

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, March 17, 2017 1:44 AM
  • Same Problem here.

    Please have a look at your telemetry. From The Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20170223_084417\Detail.txt

    --

    (01) 2017-02-23 08:45:16 Slp: Instance Name: SQLEXPRESS  PatchState: NA ReadyToInstallPatch: False ReadyToRemovePatch: False ReadyToUpgradeMsi: False
    (01) 2017-02-23 08:45:16 Slp: Instance Name SQLEXPRESS : Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:16 Slp: Shared Features PatchState: NA ReadyToInstallPatch: False ReadyToRemovePatch: False ReadyToUpgradeMsi False
    (01) 2017-02-23 08:45:16 Slp: Shared Features : Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:16 Slp: Error: Action "Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction" threw an exception during execution.
    (01) 2017-02-23 08:45:16 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Beim Ausführen des Setups wurden keine Features aktualisiert. Möglicherweise sind die angeforderten Features nicht installiert, oder sie weisen bereits eine höhere Patchebene auf. Weitere Informationen finden Sie in den Protokollen "summary.txt".
    (01) 2017-02-23 08:45:16 Slp: Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:16 Slp: Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist. ---> Microsoft.SqlServer.Configuration.MsiExtension.PatchNoopException: Beim Ausführen des Setups wurden keine Features aktualisiert. Möglicherweise sind die angeforderten Features nicht installiert, oder sie weisen bereits eine höhere Patchebene auf. Weitere Informationen finden Sie in den Protokollen "summary.txt".
    (01) 2017-02-23 08:45:16 Slp: Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:16 Slp: Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2017-02-23 08:45:16 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    (01) 2017-02-23 08:45:16 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    (01) 2017-02-23 08:45:17 Slp: Received request to add the following file to Watson reporting: C:\windows\TEMP\tmp600F.tmp
    (01) 2017-02-23 08:45:17 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2017-02-23 08:45:17 Slp: Inner exceptions are being indented
    (01) 2017-02-23 08:45:17 Slp:
    (01) 2017-02-23 08:45:17 Slp: Exception type: Microsoft.SqlServer.Configuration.MsiExtension.PatchNoopException
    (01) 2017-02-23 08:45:17 Slp:     Message:
    (01) 2017-02-23 08:45:17 Slp:         Beim Ausführen des Setups wurden keine Features aktualisiert. Möglicherweise sind die angeforderten Features nicht installiert, oder sie weisen bereits eine höhere Patchebene auf. Weitere Informationen finden Sie in den Protokollen "summary.txt".
    (01) 2017-02-23 08:45:17 Slp:         Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:17 Slp:         Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:17 Slp:     HResult : 0x86430003
    (01) 2017-02-23 08:45:17 Slp:         FacilityCode : 1603 (643)
    (01) 2017-02-23 08:45:17 Slp:         ErrorCode : 3 (0003)
    (01) 2017-02-23 08:45:17 Slp:     Data:
    (01) 2017-02-23 08:45:17 Slp:       SummaryMessage =
    Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    Das angegebene kumulative Update konnte nicht angewendet werden, weil bereits ein Service Pack oder eine GDR-Version installiert ist.
    (01) 2017-02-23 08:45:17 Slp:       WatsonData = Microsoft.SqlServer.Configuration.MsiExtension.PatchNoopException@3
    (01) 2017-02-23 08:45:17 Slp:       DisableWatson = true
    (01) 2017-02-23 08:45:17 Slp:     Stack:
    (01) 2017-02-23 08:45:17 Slp:         bei Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.GetEligiableInstances()
    (01) 2017-02-23 08:45:17 Slp:         bei Microsoft.SqlServer.Configuration.MsiExtension.SetInstanceInstallStateAction.ExecuteAction(String actionId)
    (01) 2017-02-23 08:45:17 Slp:         bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2017-02-23 08:45:17 Slp:         bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2017-02-23 08:45:17 Slp:         bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2017-02-23 08:45:17 Slp: SetupTelemetry: Writing Telemetry to Datastore
    (01) 2017-02-23 08:45:18 Slp:
    (01) 2017-02-23 08:45:18 Slp: ----------------------------------------------------------------------
    (01) 2017-02-23 08:45:18 Slp:
    (01) 2017-02-23 08:45:18 Slp: Fehlerergebnis: -2042429437
    (01) 2017-02-23 08:45:18 Slp: Ergebniseinrichtungscode: 1603
    (01) 2017-02-23 08:45:18 Slp: Ergebnisfehlercode: 3
    (01) 2017-02-23 08:45:18 Slp: SetupTelemetry: Closing Telemetry Session
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to get registry value MachineId
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\130
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to get registry value CustomerFeedback
    (01) 2017-02-23 08:45:18 Slp: Sco: Attempting to get registry value EnableErrorReporting
    (01) 2017-02-23 08:45:18 Slp: SetupTelemetry: Telemetry has an active session with 3 events.

    --

    The content of the WindowsUpdate.log is worthless with modern Windows versions and and imho the "successor" isn't much better:

    --

    Windows Update logs are now generated using ETW (Event Tracing for Windows).
    Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.


    For more information, please visit http://go.microsoft.com/fwlink/?LinkId=518345

    --

    Friday, March 17, 2017 9:10 AM
  • Hi all, could you please share the time when you tried to use Windows Update to upgrade SQL Server?

    Best Regards,

    Teige


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, March 21, 2017 6:19 AM
  • Hi all, 

    The engineers required many detailed information, could you please connect to this e-mail v-2soqur@mssupport.microsoft.com and connect with them, this will help them troubleshooting this problem. 

    Thank you,
    Teige


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Tuesday, March 21, 2017 7:12 AM
  • Hi Teige,

    I first tried installing CU1 for SQL Server 2016 SP1 with Windows Update on 22.2.201, my latest try was on 17.3.2017. The update has failed every time, but manual update completed successfully each time.

    Regards,
    Brynjar

    Tuesday, March 21, 2017 1:13 PM
  • Hi Teige,

    please share what, when (UTC) and where (WU / WSUS / WU Catalog...) has been changed with this update.

    Tuesday, March 21, 2017 3:12 PM
  • A new revision (201) of "SQL Server 2016 Service Pack 1 Cumulative Update (CU) 1" KB3208177 is available with WSUS: "Information has changed about how to install the update files."
    Wednesday, March 22, 2017 8:28 PM
  • This is no longer an issue for me since I have installed the CU 1 for SQL Server 2016 SP1 manually on all our 2016 SP1 servers.

    Microsoft has also made a new version of "SQL Server 2016 Service Pack 1 Cumulative Update (CU) 1" KB3208177 available. I have not been able to try to install it with Windows Update, so I can't verify if the new version succeeds with Windows Update.

    Cumulative Update 2 for SQL Server 2016 SP1 has also been made available now.

    Regards,
    Brynjar

    Tuesday, March 28, 2017 8:10 AM