September 21, 2017 at 3:38 pm
Corporate is making us install all windows updates on our servers, but I keep getting errors trying to install, and I tried all tricks of repairing/uninstalling old updates, but all ran into the same road block of "Service Pack 2 for SQL Server 2008 R2 (KB2630458) (64-bit)", version 10.52.4000.0. This update is shown as installed, but when i was trying to uninstall, it says "There are no SQL Server instances or shared features that can be updated on this computer." I searched online for KB2630458, but can't find anything that has version 10.52.4000.0. The only version available is 10.50.4000.0.
================================================================================
Here's my sql version:
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4297.0 (X64)
Nov 22 2013 17:24:14
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
================================================================================
Here's the typical error message I got when I try to install new updates, repair, or uninstall old - the patch file name might be different, but all are asking for (KB2630458) (64-bit), version 10.52.4000.0, which I can't find:
-----------
SQL Server Setup has encountered the following error:
The cached patch file "c:\Windows\Installer\49cb1.msp" is missing. The original file for this cached file is "sql_engine_core_inst.msp", which can be installed from "Service Pack 2 for SQL Server 2008 R2 (KB2630458) (64-bit)", version 10.52.4000.0.
For more information about how to resolve this problem, see “Steps to resolve missing media issue with SQL Server 2008 R2” (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge Base.
Error code 0x84B20003.
-----------
Any idea? Thanks!
September 21, 2017 at 4:16 pm
Those version numbers are all SP2 - Microsoft just likes to confuse everyone. The number you get back depends on whatever tool you are using but it's just SP2 (10.50 and 10.52)
You can check this thread for more information - it has a link to the connect item where MS reports "It's by design". That just means they aren't going to fix it:
SQL Server 2008 R2 SP2 buildnumber: 10.50.4000.0 or 10.52.4000.0 ?
So ignore the numbers and follow the steps in the article given in the link at the end of the article.
Sue
September 22, 2017 at 8:28 am
Thanks, Sue! Don't know why MS has to make simple things like this so confusing.
It's a very frustrating business to try to fix windows updates failures. After a lot of digging, it seems I need to run the repair. But after I ran the repair, i was told I'm missing sqlncli.msi. I downloaded the only version I can find, but it still says it's the wrong file. My server has a lot of different versions of VS and SQL. Maybe that's why it's all messed up.
September 22, 2017 at 10:22 am
Michelle-138172 - Friday, September 22, 2017 8:28 AMThanks, Sue! Don't know why MS has to make simple things like this so confusing.It's a very frustrating business to try to fix windows updates failures. After a lot of digging, it seems I need to run the repair. But after I ran the repair, i was told I'm missing sqlncli.msi. I downloaded the only version I can find, but it still says it's the wrong file. My server has a lot of different versions of VS and SQL. Maybe that's why it's all messed up.
It's not the first time they hosed out version numbers - it was worse with one they did for 2005. I guess they do it because they are good at it due to a lot of experience 🙂
It could be the different versions messing things up - the whole caching process for updates, finding previous installs is just problematic.
That link you first have in the error has a vbscript to run that tries to fix the paths to installers - it's worth trying that.
There is also a link about trying to uninstall when you have issues - not exactly the same but similiar to what you are dealing with and might give you some more things to check:
Cleanly Uninstalling Stubborn SQL Server Components
Sue
September 22, 2017 at 1:40 pm
Thanks again, Sue! Got too many errors - will rebuild the server.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply