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

Can't update SQL 2012 instance Expand / Collapse
Author
Message
Posted Thursday, September 05, 2013 1:57 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 1:25 PM
Points: 295, Visits: 865
Hi, I have an instance of SQL Server 2012 that is not being detected by the installer. I need to apply SP1 + CU5 to the instance but when I run SP setup, it does not see the instance. It finds the other instances on the box but not the one that needs the updates.

If I run from command line with /allinstances or even /instancename=xxx, it does not find it either.

The instance runs fine and shows up as it should in SQL Server Configuration Manager but I can't upgrade or add features. Any suggestions would help.

Thanks
Post #1491940
Posted Thursday, September 05, 2013 4:07 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, April 17, 2014 4:43 AM
Points: 756, Visits: 631
What does "SELECT @@version" report for this instance?

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1491988
Posted Thursday, September 05, 2013 4:33 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 1:25 PM
Points: 295, Visits: 865
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)


It shows 11.0.3000 because I installed SP1 on it before this problem began. Unfortunately, now that it is not detectable by SQL Server installation files, I can't get CU5 on it or add/remove any features from the installation.
Post #1491997
Posted Friday, September 06, 2013 1:41 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, April 17, 2014 4:43 AM
Points: 756, Visits: 631
I would double-check that you don't have CU5 for SQL 2012 RTM, and after having verified that you actually have the files for http://support.microsoft.com/kb/2861107, I would open a case with Microsoft. These kinds of issue are difficult to assist with over a forum.

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1492071
Posted Friday, September 06, 2013 7:18 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, February 11, 2014 10:12 AM
Points: 110, Visits: 501
As far as i know

We have cu9 for SQL server 2012 RTM

and

CU5 for SQL server 2012 sp1


These are the latest

http://sqlserverbuilds.blogspot.com/
Post #1492218
Posted Friday, September 06, 2013 8:11 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, March 14, 2014 10:32 AM
Points: 215, Visits: 444
Open a call with MS, this happened to me and they had to log in and fix it and no I don't remember what they did, we ran so many diags on the instance...sorry I couldn't help more.

MCSA SQL Server 2012
Post #1492258
Posted Friday, September 06, 2013 10:20 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 1:25 PM
Points: 295, Visits: 865
Thanks for the responses. I'll check into opening a case. Microsoft support is very expensive isn't it?
Post #1492328
Posted Friday, September 06, 2013 12:14 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, April 17, 2014 4:43 AM
Points: 756, Visits: 631
Yes, a support case can be expensive. But you have to weigh this against the alternatives. How much does it cost you to not being able to apply the CU? How much would it cost you to uninstall the instance and reinstall it and reapply service packs etc? Don't forget to weigh in the risk that you mess up more things so that you have to repair the other instances. Note, I'm not saying that this is necessarily more expensive than opening a case with Microsoft - if you are hobbyist working at home, maybe time is all you have. But if you are doing this as part of a full-time job, opening a case permit you spend time on all your other pressing things.

And, while maybe not that likely, this may be due to a bug in SQL Server or Windows. In such case, the support case will be without cost for you.

Before you open a case, you could try a few more last-ditch attempts: 1) Reboot windows. 2) Run SQL Server setup and try to run Repair.


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1492357
Posted Friday, September 06, 2013 12:18 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 1:25 PM
Points: 295, Visits: 865
I've tried running repair and everything else I can think of. It is a non production instance that can be rebuilt and will be phased out at some point. I was hoping that there was an easy fix that would help me to understand the internals of how SQL Server registers itself and is identified by the SP/CU installer.


Appreciate the advice.
Post #1492360
Posted Friday, September 06, 2013 12:28 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, April 17, 2014 4:43 AM
Points: 756, Visits: 631
PHXHoward (9/6/2013)
I was hoping that there was an easy fix that would help me to understand the internals of how SQL Server registers itself and is identified by the SP/CU installer.


That's some WMI/registry stuff that I have not dug too deep into, and I don't really know anyone else who does either. I mean, it works most of the time, so why bother? :--)

I understand that if this instance is not too important that you prefer to let it lie. The bitter truth is that since it works most of the time, there no easy fixes when it does not.


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1492365
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse