Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2008 R2 SP2 CU11 is continuosly failing with 'patch installer failed to update shared features' Expand / Collapse
Author
Message
Posted Wednesday, August 13, 2014 8:55 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 4:09 PM
Points: 56, Visits: 339
Hi All,

I am getting an error while updating SQL Server 2008 R2 SP2 CU11
as 'patch installer failed to update shared features'. After checking the logs the error says SQL Server 2008 R2 native client failed.
Tried reinstalling native client and it never gets reinstalled or uninstalled for some reason. I get an error as set up interrupted.

The server has 45 sql instances. Any help would be greatly appreciated.
Below is the portion of summary log and detail log

Overall summary:
Final result: The patch installer has failed to update the following instance: NV0476. To determine the reason for failure, review the log files.
Exit code (Decimal): -2068052413
Exit facility code: 1212
Exit error code: 1603
Exit message: The patch installer has failed to update the following instance: NV0476. To determine the reason for failure, review the log files.
Start time: 2014-08-13 08:01:46
End time: 2014-08-13 09:09:06
Requested action: Patch

Instance NV0476 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): -2068052413
Exit facility code: 1212
Exit error code: 1603
Exit message: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Start time: 2014-08-13 09:04:18
End time: 2014-08-13 09:08:56
Requested action: Patch
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4319.0

Machine Properties:
Machine name: SPRPQDISPDB01
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Detail log
----------

2014-08-13 09:08:41 Slp: Sco: Attempting to set value SQL_WRITER
2014-08-13 09:08:41 Slp: SetValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState, Name = SQL_WRITER
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_Engine_Core_Shared_sql_engine_core_shared_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Shared_sql_engine_core_shared_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_Engine_Core_Shared_sql_engine_core_shared_Cpu64. There are 7 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_PowerShell_Engine_CNS_sql_engine_core_shared_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_PowerShell_Engine_CNS_sql_engine_core_shared_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_PowerShell_Engine_CNS_sql_engine_core_shared_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_Engine_Core_Shared_sql_engine_core_shared_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_DTS_Full_sql_is_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_DTS_Full_sql_is_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_DTS_Full_sql_is_Cpu64. There are 10 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_BIDS_Full_sql_bids_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_BIDS_Full_sql_bids_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_BIDS_Full_sql_bids_Cpu64. There are 9 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_SSMS_Adv_sql_ssms_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_SSMS_Adv_sql_ssms_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_SSMS_Adv_sql_ssms_Cpu64. There are 12 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_PowerShell_Tools_ANS_sql_ssms_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_PowerShell_Tools_ANS_sql_ssms_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_PowerShell_Tools_ANS_sql_ssms_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SSMS_Adv_sql_ssms_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_Tools_Legacy_Full_sql_tools_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_Tools_Legacy_Full_sql_tools_Cpu64_Patch_Finalize_finalize The condition tests feature: Tools_Legacy_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SDK_Full_sql_tools_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SDK_Full_sql_tools_Cpu64_Patch_Finalize_finalize The condition tests feature: SDK_Full_sql_tools_Cpu64. There are 5 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_SSMS_Full_sql_tools_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_SSMS_Full_sql_tools_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_SSMS_Full_sql_tools_Cpu64. There are 3 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SSMS_Adv_sql_ssms_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_Connectivity_Full_sql_tools_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_Connectivity_Full_sql_tools_Cpu64_Patch_Finalize_finalize The condition tests feature: Connectivity_Full_sql_tools_Cpu64. There are 6 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_SNAC_CORE_sqlncli_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_Engine_Core_Shared_sql_engine_core_shared_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-08-13 09:08:41 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:41 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There are 3 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:41 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-08-13 09:08:42 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_finalize" will return false due to the following conditions:
2014-08-13 09:08:42 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_finalize The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results: ValidateResult, Result, CleanupResult." did not pass as it returned false and true was expected.
2014-08-13 09:08:42 Slp: Condition is false because the required feature SQL_FullText_Core_Shared_sql_engine_core_shared_Cpu64 failed in result Result
2014-08-13 09:08:42 Slp: Completed Action: FinalizeTimingConfigAction, returned True
2014-08-13 09:08:42 Slp: ----------------------------------------------------------------------
2014-08-13 09:08:42 Slp: Running Action: CreateARPRegKeyAction
2014-08-13 09:08:42 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-08-13 09:08:42 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Windows\CurrentVersion\Uninstall\KB2967540
2014-08-13 09:08:42 Slp: Sco: Attempting to get registry value SQLProductPatchFamilyCode
2014-08-13 09:08:42 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Windows\CurrentVersion\Uninstall
Post #1602790
Posted Friday, August 15, 2014 10:57 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:21 AM
Points: 21, Visits: 159
This:
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log

is the key to your first door. However, if the summary and detail are not from the very first failure, you may be in a maze, where the key you have is to some door, but perhaps not the first door.
Post #1604013
Posted Wednesday, August 20, 2014 7:39 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 4:09 PM
Points: 56, Visits: 339
Thanks for the reply. sqlncli_Cpu64_1.log gives error as SQL Server 2008 R2 native client failed. However as mentioned earlier i am unable to make any changes to native client on this server.

Any help fould be greatly appreciated.

Regards,
Hidayath
Post #1605431
Posted Wednesday, August 20, 2014 7:45 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 4:09 PM
Points: 56, Visits: 339
Thanks for the reply. sqlncli_Cpu64_1.log gives error as SQL Server 2008 R2 native client failed. However as mentioned earlier i am unable to make any changes to native client on this server.

Any help would be greatly appreciated.

Regards,
Hidayath
Post #1605442
Posted Wednesday, August 20, 2014 11:28 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:21 AM
Points: 21, Visits: 159
Yes.

You must find the reason why Native Client had failed. Based upon the discovered reason, you must take an action before attempting another install. The action you must take depends upon what C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log states is the error.


However, if C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is not the very first setup error (i.e. if the first setup error's date & time was not 2014-08-13T08:00:58), you must find the very first summary text file for the very first setup failure, under a folder that is named C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\YYYYMMDD_HHMMSS. The summary text file within that folder might point you to a sqlncli_Cpu64_1.log file. The log file will not be in the same folder as the sqlncli_Cpu64_1.log file (mentioned above). You must inspect those setup files, not the latest files, for the cause of the very first failure.

To state the above in another way:
{
If C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is the file for the earliest setup failure, than that is the file that needs to be inspected. You did not provide us with that file.

On the other hand, I\f C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140813_080058\NV0476\sqlncli_Cpu64_1.log is not the file being pointed to by the EARLIEST setup failure's summary text file, the log file is academically interesting but pragmatically useless - you must uncover the very first error.
}

For example, if that very first summary text file for the very first setup error reported that a reboot is required, and if you have not rebooted Windows since that time, then all subsequent setup attempts will fail and you must reboot Windows.

As another example, if you see a message that says setup was interrupted (please paste in complete and verbatim error messages, not colloquial summaries of them), you must address why the setup had been interrupted (my use of the past tense is intentional). The cause for that interruption will definitely not be within the latest setup files. You will only see a message about setup being interrupted when you try to run setup again, but without having addressed/fixed the cause of that interruption. In this example, the cause of the original setup error (the interrupted setup) will always be within an earlier setup file.
Post #1605543
Posted Thursday, August 21, 2014 5:49 AM This worked for the OP Answer marked as solution
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 4:09 PM
Points: 56, Visits: 339
Thanks for the response. Finally the issue is resolved.

Successfully installed CU13 for one instance on the server.
I followed the workaround to copy sql server 2008 r2 native client dll(sqlncli10.dll) from other servers and CU13 was successful. Finally CU13 was successful for one instance and i will install CU13 on remaining instances tomorrow after server reboot as setup needed server reboot.
Below were the list of work arounds followed to resolve the issue.

The workaround on step7 finally resolved the issue

"1. Repaired the shared features still CU failed with same error"
"2.Repaired the sql server instance for one instance and it
failed with same error"
"3.Tried Uninstalling sql server native client and then reinstalled it
http://social.technet.microsoft.com/Forums/sqlserver/en-US/8f08ffe1-da21-4e90-b1ca-07a430332975/sql-server-2008-r2-sp2-cu11-failing-with-error-patch-installer-failed-to-update-the-shared-features?forum=sqldatabaseengine. After reboot CU again failed with same error"
"4. Looked for Missing MSI/MSP files. There are no missing
MSI/MSP files"
"5.Changed the sql server agent to local system and back to
service account and tried applying CU. CU failed with same error"
"6.uninstalled existing CU4 and tried directly installed Cu11.
Still fails with same error"
"7.Copied the sqlncli.dll from other server
to system32. Reinstalled CU and it was successful"
Post #1605764
Posted Thursday, August 21, 2014 8:09 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, October 16, 2014 10:21 AM
Points: 21, Visits: 159
Glad to see setup completed. However, you still need to perform a root cause analysis. The dates on your parallel MSDN post go back to 7/3. The date on the above setup is 8/13. You need to find the cause of the first setup failure, so you can avoid the same thing happening again.

Running msiexec /X is outside the control and knowledge of SQL Server setup. When that command is run, you put the system in an inconsistent state. The next install of a CU may fail with the same original setup failure, or the next install of a CU may fail with a different error. I have seen a few boxes that needed to be flattened after running msiexec /X. With 45 instances, I would think the cost of a msiexec /X-induced setup failure is very high. Dealing with just the error that is currently in front of you is risky.

Let me offer you an analogy: You are in a car driving in a city with many streets. You take a left turn onto a on-way street, going the wrong way. You make a right run onto a street that is marked "Residents only". You take a left turn onto a street with a road block & sign that says "Bridge under construction". You drive around the road block and your car goers off the bridge and into the water. You ask for help, but all you tell those that you ask is "My car is in the water". Someone says "Use my pump." You pump out the water, try the engine and it starts. You believe you are good to go. Is the care really fixed? What if other parts are still corroding? What if you still go the wrong way down a one -way street, you still go on a street that is marked "residents only", you still drive around a "bridge under construction" sign, or you still pump out the water from your car whenever it gets flooded?

If a setup states that a reboot is required, are you going to wait until tomorrow (and try to run SQL Server upon an incomplete setup), or are you going to immediately reboot (because you do not know how an incompletely setup SQL Server will behave)? What if setup's need to reboot the system is rooted in a module that is common to all 45 instances? The need to reboot the OS (as opposed to a need to restart just one instance of SQL Server, which SQL Server setup does easily perform) implies that all 45 instances of SQL Server will be running in an unsupported state (being exposed to the risk of random failures), until that reboot is done...

It very well could be that a reboot was required for the last successful setup, a setup that had completed before the first setup failure... If that is the cause, it is important to not postpone reboots (especially when 45 instances are setup).

A decision to setup 45 instances has consequences, and it appears those consequences were not clearly understood by the person or persons who made that decision.
Post #1605835
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse