The patch installer has failed to update the shared features.
The patch installer has failed to update the shared features. To determine the reason for failure, review the log files
Issue: The SQL server 2008 R2,CU13 upgrade installer failed with the error in Log as “The patch installer has failed to update the shared features. To determine the reason for failure, review the log files The Upgrade log
Overall summary:
Final result: The patch installer has failed to update the following instance: INST1 INST2. To determine the reason for failure, review the log files.
Exit code (Decimal):-2068578304
Exit facility code:1204
Exit error code: 0
Exit message: The patch installer has failed to update the following instance: INST1 INST2. To determine the reason for failure, review the log files.
Solutions: please follow the below solutions to resolve the issue.
Solution1:
- Before you try to install a cumulative update for the first time, rename the <System Drive>:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll file.
- If you have already tried to install a cumulative update and failed, rename the <System Drive>:\Windows\system32\perf-MSSQL10_50.MSSQLSERVER-sqlagtctr.dll, and then run the SQL Server repair process.
Try installing the CU for SQL once the above steps done.
Solution 2:To work around this problem, copy the existing Devenv.exe.config file from the following location to another copy that is named Devenv.exe.config.tmp..
drive:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\
And then run Setup again:
Solution 3: Copy the file SQSRVRES.DLL from C:\Program Files\Microsoft SQL Server\MSSQL10_50.<instance_name>\MSSQL\Binn\ to C:\Windows\System32\ and start the upgrade
Solution 4: Repair the shared components and then re-run the update.
Solution 5:Ensure to have a disk space available.
Solution 6: Repair the .NET Framework from Add Remove Program >Highlight .Net Framework 3.5 Sp1 >Select Change >Repair .
Run the update again
Note: The above resolutions apply all the Cu, Patches for SQL
Note: I resolved the issue by above Method. If you find a different solution, please report it as a comment to this post. This will be useful to SharePoint Community. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.