locked
Cumulative Update complete with Failure RRS feed

  • Question

  • HI guys,

    Today I have download the cumulative update for sql server.

    After installing the update its showing update installation complete with failures

    1.Database Engine services failed.?

    2.SQL server Replication failed ??

    3.How to resolved this ??

    what might be the issue ?

    Is this effect on anything  ?

    Looks like everything is asusual but why this failure was occured while installing..??

    Please find the screenshot below ..........

    Thanks....


    Ram

    Wednesday, March 4, 2020 1:39 PM

All replies

  • Hi Topen Tech,

    did you check the log file on C:\Program Files\Microsoft SQL Server\<m.n>\Setup Bootstrap\log ? did you also get an error window before finishing the process?

    Wednesday, March 4, 2020 1:56 PM
  • At the bottom of that message there is a hyperlink to open the installation log file; review that for more details.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Wednesday, March 4, 2020 2:19 PM
    Answerer
  • Hi @Gonzalo and @Olaf

    Thanks for the quick responce;

    please find the Summery file below.Please suggest...

    Overall summary:
      Final result:                  The patch installer has failed to update the following instance: MCAFEESERVER. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2036006904
      Start time:                    2020-03-04 17:42:17
      End time:                      2020-03-04 17:56:40
      Requested action:              Patch

    Instance MCAFEESERVER overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2036006904
      Start time:                    2020-03-04 17:46:13
      End time:                      2020-03-04 17:55:20
      Requested action:              Patch

    Machine Properties:
      Machine name:                  MCAFEE-SERVER
      Machine processor count:       2
      OS version:                    Microsoft Windows Server 2016 Standard (10.0.14393)
      OS service pack:               
      OS region:                     India
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
      SQL Server 2016      MCAFEESERVER         MSSQL13.MCAFEESERVER           Database Engine Services                 1033                 Express Edition      13.0.1745.2     No         Yes       
      SQL Server 2016      MCAFEESERVER         MSSQL13.MCAFEESERVER           SQL Server Replication                   1033                 Express Edition      13.0.1745.2     No         Yes       

    Package properties:
      Description:                   Microsoft SQL Server 2016 
      ProductName:                   SQL Server 2016
      Type:                          RTM
      Version:                       13
      SPLevel:                       2
      KBArticle:                     KB4052908
      KBArticleHyperlink:            http://support.microsoft.com/?kbid=4052908
      PatchType:                     SP
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    13.2.5026.0
      ProductVersion:                13.0.1601.5
      GDRReservedRange:              13.0.1700.0:13.0.1899.0;13.0.4200.0:13.0.4299.0
      Installation location:         e:\a8a0781dcc787b4b06\x64\setup\

    Updated product edition:
      Instance             Edition             
      MCAFEESERVER         Express             

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

    Rules with failures:

    Global rules:

    There are no scenario-specific rules.

    Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20200304_174139\SystemConfigurationCheck_Report.htm


    Ram

    Wednesday, March 4, 2020 4:31 PM
  • That log file did not say much. You will have to dig deeper. There is a file detail.txt. I think is the best one to look it - except that it is very verbose. You may have to find a place to upload it to, so that we can look at it.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Wednesday, March 4, 2020 11:01 PM
  • That log file did not say much. You will have to dig deeper. There is a file detail.txt. I think is the best one to look it - except that it is very verbose. You may have to find a place to upload it to, so that we can look at it.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    https://drive.google.com/open?id=1uYSSAmjbZSu_feGUS2YRHFrta4jEn_hT

    Please find the detail.txt log in above link


    Ram

    Thursday, March 5, 2020 1:31 AM
  • Hi Ram,

    From your detail log, it seems you missing some msi file. Could you please download SQL server setup file  from MS download link again? And run the setup file as administrator?  Or you can try to download a really cool little utility that can help you fix the missing MSIs, or at least help you identify them.  Please refer to Service Pack – Fix Missing MSI issue  and Fixing MSI errors during patching to get more information.

    Best regards,
    Cathy 

    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 5, 2020 9:05 AM
  • From your detail log, it seems you missing some msi file.

    Cathy, how do you conclude that?

    I looked quickly at the log, and I found this:

    Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: User has canceled. ---> Microsoft.SqlServer.Chainer.Infrastructure.CancelException: User has canceled.

    I am not sure how to intepret this. It sounds as if Ramjust pressed the Cancel button, but supposedly he would be aware of that he did. But maybe he was flipping around with the mouse and did it unintentional? We have all done mistakes like that.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Thursday, March 5, 2020 11:43 AM
  • Erland,

    First i did installed the update and installation completed with error shown in below picture.

    So I tried to re install the patch again, at the time it asked me to restart the server to proceed to further installation of the update.

    As I dont want to restart the server at that time I cancelled that.

    Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: User has canceled. ---> Microsoft.SqlServer.Chainer.Infrastructure.CancelException: User has canceled

    The above might be indicating that..



    Ram

    Thursday, March 5, 2020 2:33 PM
  • First i did installed the update and installation completed with error shown in below picture.

    So I tried to re install the patch again, at the time it asked me to restart the server to proceed to further installation of the update.

    As I dont want to restart the server at that time I cancelled that.

    Ah, that explains it!

    Then we need the Detail.txt for the previous attempt. There is one folder for each installation attempt. You should be able to tell from the dates which is the one that failed.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Thursday, March 5, 2020 10:44 PM