none
SQL Server 2012 SP1 --> SP2 update failure mystery

    Question

  • Successfully applied SP1 to SQL Server 2012 default SQL instance, but then subsequent application of SP2 resulted in this:

    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 code: 1603

    Log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20170103_222937\MSSQLSERVER\SqlSupport_Cpu64_1.log

    Error installing SQL Server Setup Support Files

    =====================================================================================

    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       2
      KBArticle:                     KB2958429
      KBArticleHyperlink:            http://support.microsoft.com/?kbid=2958429
      PatchType:                     SP
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    11.2.5058.0
      ProductVersion:                11.0.2100.60
      GDRReservedRange:              11.0.5300.0:11.0.5499.0
      PackageName:                   SQLServer2012-KB2958429-x64.exe
      Installation location:         i:\436c93336d4db677236e2f87\x64\setup\
    ==========================================================================

    I'm tired and can't interpret contents of SqlSupport_Cpu64_1.log file:

    === Verbose logging started: 1/3/2017  22:00:26  Build type: SHIP UNICODE 5.00.7601.00  Calling process: i:\436c93336d4db677236e2f87\x64\ScenarioEngine.exe ===
    MSI (c) (A0:44) [22:00:26:372]: Resetting cached policy values
    MSI (c) (A0:44) [22:00:26:372]: Machine policy value 'Debug' is 0
    MSI (c) (A0:44) [22:00:26:372]: ******* RunEngine:
               ******* Product: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (A0:44) [22:00:26:372]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (A0:44) [22:00:26:372]: Grabbed execution mutex.
    MSI (c) (A0:44) [22:00:26:372]: Cloaking enabled.
    MSI (c) (A0:44) [22:00:26:372]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (A0:44) [22:00:26:372]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (74:30) [22:00:26:387]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi
    MSI (s) (74:30) [22:00:26:387]: Grabbed execution mutex.
    MSI (s) (74:04) [22:00:26:387]: MainEngineThread is returning 1603
    MSI (s) (74:30) [22:00:26:387]: User policy value 'DisableRollback' is 0
    MSI (s) (74:30) [22:00:26:387]: Machine policy value 'DisableRollback' is 0
    MSI (s) (74:30) [22:00:26:387]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (74:30) [22:00:26:387]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (74:30) [22:00:26:387]: Restoring environment variables
    MSI (c) (A0:44) [22:00:26:387]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (A0:44) [22:00:26:387]: MainEngineThread is returning 1603
    === Verbose logging stopped: 1/3/2017  22:00:26 ===

    Can anybody give me ideas on how to go about troubleshooting this failure & getting SP2 applied successfully?

    Thanks,


    Phil Streiff, MCDBA, MCITP, MCSA

    • Edited by philfactor Wednesday, January 4, 2017 4:59 AM
    Wednesday, January 4, 2017 4:57 AM

Answers

  • Hey Phil,

    As per my experience with CU or SP update on SQL server; It is always the case of either missing setup files from windows installer cache or Reboot pending from earlier Update on Windows level.

    In your case, can you check if support file MSI is in plcae or not?

    C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi

    Thanks,


    Kindly mark the reply as answer if they help

    Wednesday, January 4, 2017 5:15 AM
  • Hi Phil,

    I think Sunil has a point here and I would also suggest you locate and upload corresponding details.txt and summary.txt and share the link here so we can take a further look into the issue. 

    >>MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

    At this moment, all I can see is some registry keys could not be opened(1402) and the file could not be found(2).

    If you have any other questions, please let me know.

    Regards,
    Lin


    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.

    • Marked as answer by philfactor Wednesday, January 4, 2017 3:14 PM
    Wednesday, January 4, 2017 6:58 AM
    Moderator

All replies

  • Hey Phil,

    As per my experience with CU or SP update on SQL server; It is always the case of either missing setup files from windows installer cache or Reboot pending from earlier Update on Windows level.

    In your case, can you check if support file MSI is in plcae or not?

    C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2958429\ServicePack\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi

    Thanks,


    Kindly mark the reply as answer if they help

    Wednesday, January 4, 2017 5:15 AM
  • Hi Phil,

    I think Sunil has a point here and I would also suggest you locate and upload corresponding details.txt and summary.txt and share the link here so we can take a further look into the issue. 

    >>MSI (s) (74:30) [22:00:26:387]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

    At this moment, all I can see is some registry keys could not be opened(1402) and the file could not be found(2).

    If you have any other questions, please let me know.

    Regards,
    Lin


    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.

    • Marked as answer by philfactor Wednesday, January 4, 2017 3:14 PM
    Wednesday, January 4, 2017 6:58 AM
    Moderator
  • Well, it turns out there was a pending reboot operation that was preventing successful SP2 update. Once the server was rebooted, that apparently cleared the blocker and I was able to successfully install SP2 without issue.

    Apparently, the 'pending reboot' check in preinstall checklist of SP2 install missed this or didn't work properly, because there was no warning and it allowed install to proceed all the way to the end, where it ultimately failed.

    The bad thing is that I went through all the Setup bootstrap logs I could find and didn't see any messages that indicated a pending reboot caused failed SP2 installation. It could have saved me a lot of time if that was more clear. Maybe I just didn't know how to find such an error message.

    I would appreciate feedback on these 2 items:

    1) What does a 'pending reboot' error in Setup bootstrap logs look like so I can find it faster the next time?

    2) What is a reliable and simple way to determine if there is a pending reboot operation on Windows Server 2008 R2? (I've seen suggestions for looking at specific keys in Registry, surely that's not the only way)

    Thanks Sunil & Lin!


    Phil Streiff, MCDBA, MCITP, MCSA

    • Edited by philfactor Wednesday, January 4, 2017 8:29 PM
    Wednesday, January 4, 2017 3:14 PM