question

KrisT_SQL avatar image
KrisT_SQL asked

SQL Server 2016 (Enterprise Edition) SP2/CU5 and SP2/CU6 Fail

Another engineer built this Windows Server a couple months ago and installed SQL Server 2016/RTM. He patched SQL Server with latest SP's and CU's (which was SP2/CU4 at that time and still today). In February I attempted to upgrade this instance to SP2/CU5 and All Features Failed. On 4/27 I tried to patch this SQL Server again but with SP2/CU6 and half of the Features Failed and half Succeeded.

SP2/CU6 Install Results:

SP2/CU6 Error Log:
=== Verbose logging started: 4/28/2019 6:24:31 Build type: SHIP UNICODE 5.00.9600.00 Calling process: E:\6f6103bd891bf837eb82d10da71fb538\x64\ScenarioEngine.exe === MSI (c) (CC:7C) [06:24:31:735]: Resetting cached policy values MSI (c) (CC:7C) [06:24:31:735]: Machine policy value 'Debug' is 0 MSI (c) (CC:7C) [06:24:31:735]: ******* RunEngine: ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C} ******* Action: ******* CommandLine: ********** MSI (c) (CC:7C) [06:24:31:735]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (CC:7C) [06:24:31:735]: Grabbed execution mutex. MSI (c) (CC:7C) [06:24:31:735]: Cloaking enabled. MSI (c) (CC:7C) [06:24:31:735]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (CC:7C) [06:24:31:735]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (2C:4C) [06:24:31:735]: Running installation inside multi-package transaction {57846DA8-8B5D-4466-B850-E8CDFC94046C} MSI (s) (2C:4C) [06:24:31:735]: Grabbed execution mutex. MSI (s) (2C:30) [06:24:31:735]: Resetting cached policy values MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'Debug' is 0 MSI (s) (2C:30) [06:24:31:735]: ******* RunEngine: ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C} ******* Action: ******* CommandLine: ********** MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (2C:30) [06:24:31:735]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038 MSI (s) (2C:30) [06:24:31:735]: SRSetRestorePoint skipped for this transaction. MSI (s) (2C:30) [06:24:31:735]: End dialog not enabled MSI (s) (2C:30) [06:24:31:735]: Original package ==> C:\Windows\Installer\1842ef5.msi MSI (s) (2C:30) [06:24:31:735]: Package we're running from ==> C:\Windows\Installer\1842ef5.msi MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall Flags override found. MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall VersionNT override found. MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall ServicePackLevel override found. MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: looking for appcompat database entry with ProductCode '{57846DA8-8B5D-4466-B850-E8CDFC94046C}'. MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2 MSI (s) (2C:30) [06:24:31:751]: File will have security applied from OpCode. MSI (s) (2C:30) [06:24:31:751]: Original patch ==> E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp MSI (s) (2C:30) [06:24:31:751]: Patch we're running from ==> C:\Windows\Installer\49e70.msp MSI (s) (2C:30) [06:24:31:751]: Opening existing patch 'C:\Windows\Installer\89322.msp'. MSI (s) (2C:30) [06:24:31:751]: 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) (2C:30) [06:24:31:751]: PATCH SEQUENCER: verifying the applicability of QFE patch E:\6f6103bd891bf837eb82d10da71fb538\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) (2C:30) [06:24:31:751]: PATCH SEQUENCER: QFE patch E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp is not applicable. MSI (s) (2C:30) [06:24:31:751]: SequencePatches returns success. MSI (s) (2C:30) [06:24:31:751]: Final Patch Application Order: MSI (s) (2C:30) [06:24:31:751]: Other Patches: MSI (s) (2C:30) [06:24:31:751]: Unknown\Absent: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0} - E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files - Update '{D20E0888-BDCC-40E9-8EA7-3293D389DCC0}' 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\20190428_062233\MSSQLSERVER\sql_common_core_Cpu64_1.log. MSI (s) (2C:30) [06:24:31:751]: 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: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0}. Installation success or error status: 1642. MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1708 MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files -- Installation failed. MSI (s) (2C:30) [06:24:31:751]: 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) (2C:30) [06:24:31:751]: Attempting to delete file C:\Windows\Installer\49e70.msp MSI (s) (2C:30) [06:24:31:751]: MainEngineThread is returning 1642 MSI (s) (2C:4C) [06:24:31:751]: 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\1842ef5.msi MSI (s) (2C:4C) [06:24:31:751]: User policy value 'DisableRollback' is 0 MSI (s) (2C:4C) [06:24:31:751]: Machine policy value 'DisableRollback' is 0 MSI (s) (2C:4C) [06:24:31:751]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (2C:4C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (CC:7C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (CC:7C) [06:24:31:751]: MainEngineThread is returning 1642 === Verbose logging stopped: 4/28/2019 6:24:31 ===

sql server
4 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ThomasRushton avatar image ThomasRushton ♦♦ commented ·

The message says "Product: SQL Server 2016 Common Files - Update '{D20E0888-BDCC-40E9-8EA7-3293D389DCC0}' 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\20190428_062233\MSSQLSERVER\sql_common_core_Cpu64_1.log."

So, what's in that file?

0 Likes 0 ·
ThomasRushton avatar image ThomasRushton ♦♦ commented ·

Also, please provide the results of `select @@version`

0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·

What happens if you try to reinstall CU4?

0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·

Can you post the contents of the file named summary_XXXXXXX.txt in the same folder. You might want to obfuscate any sensitive detail in there first

0 Likes 0 ·
KrisT_SQL avatar image
KrisT_SQL answered

Solution To Patching Error:

After referencing the article below by Pinal Dave (SQL Authority) I used the Repair Wizard which basically replaced the missing file that was previously causing patches to fail. During maintenance window last night I ran the Repair Wizard and it completed successfully. Next I attempted to run sp2\cu8 (this is current patch level of other servers) and current build # of for this particular sql instance was sp2\cu4 (13.0.5233.0) but it failed. I restarted Windows Server (which is necessary after patch failure) then I attempted to install sp2 because error messaging from previous failures which was successful. Then again I attempted sp2\cu8 and it too was successful on all components.

*** I did have to request sql 2016 installation media from AWS since our sql licensing is through AWS before I was able to run the Repair Wizard.

https://blog.sqlauthority.com/2018/04/28/sql-server-service-pack-failure-missingregistrykeyexception-the-registry-key-is-missing/

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

The log file is posted above... it is referencing itself. I copied and pasted the above file path into file explorer and I verified that it is the same error log as what I posted above.

Select @@Version returns:

Microsoft SQL Server 2016 (SP2-CU4) (KB4464106) - 13.0.5233.0 (X64) Nov 3 2018 00:01:54 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)


ssc-select.png (23.6 KiB)
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

@@Kev RIley I tried to reinstall CU4 also on 4/27 after searching google... but it failed also. I had a difficult time finding CU4 because when i tried to download it from https://sqlserverbuilds.blogspot.com/ it kept forcing me to CU6. But I was able to find it here and download from https://www.catalog.update.microsoft.com/search.aspx?q=sql%20server

2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Kev Riley avatar image Kev Riley ♦♦ commented ·

What did it fail with then? Or do you not recall?

0 Likes 0 ·
KrisT_SQL avatar image KrisT_SQL commented ·

I do not recall which components CU4 failed on. I believe it failed/succeeded on the same components as CU6 in screenshot above. I did not take screenshot of CU4 failure. I am confused as to why all components failed on CU5, then CU6 succeeded on half and failed on other half.

0 Likes 0 ·
Kev Riley avatar image
Kev Riley answered

The key here seems to be the message:

Unknown\Absent: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0} - E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp

Can you verify that that file exists? Or maybe the folder gets/got cleaned up after a failed install.

5 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image KrisT_SQL commented ·

this file does not exist. how do I get it?

0 Likes 0 ·
Show more comments
KrisT_SQL avatar image KrisT_SQL commented ·

E:\6f6103bd891bf837eb82d10da71fb538\x64
this part of the file path exist

0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·

This folder will have been created by the patch - it essentially un-packs all of it's compressed files into directory, runs the install, and then should clean up.

I would be tempted to re-download the patches (prob starting at CU4), remove or at least rename or move that E:\6f6103bd891bf837eb82d10da71fb538 folder, and attempt a clean patch. I would say to re-download just in case the downloads you have are damaged in some way

0 Likes 0 ·
Kev Riley avatar image Kev Riley ♦♦ commented ·

Also, what state does Windows Update say that it is in? Maybe a patch via Windows Update clashed with a manually applied patch, leaving the machine in this state.

0 Likes 0 ·
KrisT_SQL avatar image
KrisT_SQL answered

I do not recall the exact components that it failed on.

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

the windows updates all installed successfully. I believe I stopped the windows updates because it was stuck and restarted them again. So the failures are because i stopped updates and restarted process


10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

just found screenshot of SP2/CU4 installation.


sp2-cu4-error.png (194.7 KiB)
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

@Kev Riley My manager would like to leave as is until next maintenance window on 5/18. This server is on SP2/CU4 and Primary for an AG but both secondary replicas are on SP2/CU6. I do not see any major risk of waiting until next maintenance window. Are there any known risk that I am not aware of?

I have a maintenance window scheduled for 5/18 and will update this post then.

@Kev Riley Thanks for your help it is appreciated!!

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KrisT_SQL avatar image
KrisT_SQL answered

@Kev Riley This past Saturday 5/18 i had my scheduled maintenance window where i did as you recommended above but unfortunately I am still receiving the same error. I removed the that E:\6f6103bd891bf837eb82d10da71fb538 folder, re-downloaded sql patches (sp2 cu4, cu5 & cu6). It still continues to fail... same error message just different file name

Error Message for sp2/cu4:

=== Verbose logging started: 5/19/2019 6:40:02 Build type: SHIP UNICODE 5.00.9600.00 Calling process: E:\8537cd18e2054e3b2fece6d5f564\x64\ScenarioEngine.exe === MSI (c) (58:84) [06:40:02:263]: Resetting cached policy values MSI (c) (58:84) [06:40:02:263]: Machine policy value 'Debug' is 0 MSI (c) (58:84) [06:40:02:263]: ******* RunEngine: ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C} ******* Action: ******* CommandLine: ********** MSI (c) (58:84) [06:40:02:263]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (58:84) [06:40:02:263]: Grabbed execution mutex. MSI (c) (58:84) [06:40:02:263]: Cloaking enabled. MSI (c) (58:84) [06:40:02:263]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (58:84) [06:40:02:263]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (58:C8) [06:40:02:263]: Running installation inside multi-package transaction {57846DA8-8B5D-4466-B850-E8CDFC94046C} MSI (s) (58:C8) [06:40:02:263]: Grabbed execution mutex. MSI (s) (58:E8) [06:40:02:279]: Resetting cached policy values MSI (s) (58:E8) [06:40:02:279]: Machine policy value 'Debug' is 0 MSI (s) (58:E8) [06:40:02:279]: ******* RunEngine: ******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C} ******* Action: ******* CommandLine: ********** MSI (s) (58:E8) [06:40:02:279]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (58:E8) [06:40:02:279]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038 MSI (s) (58:E8) [06:40:02:279]: SRSetRestorePoint skipped for this transaction. MSI (s) (58:E8) [06:40:02:279]: End dialog not enabled MSI (s) (58:E8) [06:40:02:279]: Original package ==> C:\Windows\Installer\1842ef5.msi MSI (s) (58:E8) [06:40:02:279]: Package we're running from ==> C:\Windows\Installer\1842ef5.msi MSI (s) (58:E8) [06:40:02:279]: APPCOMPAT: Uninstall Flags override found. MSI (s) (58:E8) [06:40:02:279]: APPCOMPAT: Uninstall VersionNT override found. MSI (s) (58:E8) [06:40:02:279]: APPCOMPAT: Uninstall ServicePackLevel override found. MSI (s) (58:E8) [06:40:02:279]: APPCOMPAT: looking for appcompat database entry with ProductCode '{57846DA8-8B5D-4466-B850-E8CDFC94046C}'. MSI (s) (58:E8) [06:40:02:279]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (58:E8) [06:40:02:279]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2 MSI (s) (58:E8) [06:40:02:279]: File will have security applied from OpCode. MSI (s) (58:E8) [06:40:02:279]: Original patch ==> E:\8537cd18e2054e3b2fece6d5f564\x64\setup\sql_common_core_msi\sql_common_core.msp MSI (s) (58:E8) [06:40:02:279]: Patch we're running from ==> C:\Windows\Installer\1025da.msp MSI (s) (58:E8) [06:40:02:279]: Opening existing patch 'C:\Windows\Installer\89322.msp'. MSI (s) (58:E8) [06:40:02:279]: 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) (58:E8) [06:40:02:279]: PATCH SEQUENCER: verifying the applicability of QFE patch E:\8537cd18e2054e3b2fece6d5f564\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) (58:E8) [06:40:02:279]: PATCH SEQUENCER: QFE patch E:\8537cd18e2054e3b2fece6d5f564\x64\setup\sql_common_core_msi\sql_common_core.msp is not applicable. MSI (s) (58:E8) [06:40:02:279]: SequencePatches returns success. MSI (s) (58:E8) [06:40:02:279]: Final Patch Application Order: MSI (s) (58:E8) [06:40:02:279]: Other Patches: MSI (s) (58:E8) [06:40:02:279]: Unknown\Absent: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0} - E:\8537cd18e2054e3b2fece6d5f564\x64\setup\sql_common_core_msi\sql_common_core.msp MSI (s) (58:E8) [06:40:02:279]: Product: SQL Server 2016 Common Files - Update '{D20E0888-BDCC-40E9-8EA7-3293D389DCC0}' 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\20190519_063904\MSSQLSERVER\sql_common_core_Cpu64_1.log. MSI (s) (58:E8) [06:40:02:279]: 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: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0}. Installation success or error status: 1642. MSI (s) (58:E8) [06:40:02:279]: Note: 1: 1708 MSI (s) (58:E8) [06:40:02:279]: Product: SQL Server 2016 Common Files -- Installation failed. MSI (s) (58:E8) [06:40:02:279]: 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) (58:E8) [06:40:02:279]: Attempting to delete file C:\Windows\Installer\1025da.msp MSI (s) (58:E8) [06:40:02:279]: MainEngineThread is returning 1642 MSI (s) (58:C8) [06:40:02:279]: 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\1842ef5.msi MSI (s) (58:C8) [06:40:02:279]: User policy value 'DisableRollback' is 0 MSI (s) (58:C8) [06:40:02:279]: Machine policy value 'DisableRollback' is 0 MSI (s) (58:C8) [06:40:02:279]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (58:C8) [06:40:02:279]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (58:C8) [06:40:02:279]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 MSI (s) (58:C8) [06:40:02:279]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (58:84) [06:40:02:279]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (58:84) [06:40:02:279]: MainEngineThread is returning 1642 === Verbose logging stopped: 5/19/2019 6:40:02 ===

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.