none
SQL 2014 SP2 does not allow to select instance to apply patch.

    Question

  • Hi,

    I have 11 SQL instances running on single virtual box and it is SQL 2014 standard edition SP1 CU5.

    I am trying to apply SP2 on all 11 instances. But when I reach 'select features' tab, I am not able to select any single instance to proceed.

    can you please help me why I am not able to select and how can I fix the issue?

    Hope to hear soon.

    Regards,

    Nik


    Regards, Naman

    Wednesday, February 1, 2017 7:42 AM

All replies

  • First quick question, do you have the correct architecture of the service pack (32-bit vs. 64-bit) that matches the instances?

    Can you run the Discovery Report to see what SQL Server setup detects in terms of versions? Here's a link to the steps for 2012, but it is the same for 2014.

    https://blogs.msdn.microsoft.com/samlester/2013/06/13/sql-server-2012-discovery-report-determining-what-sql-server-components-are-installed/

    Also, can you provide a screenshot of the feature selection page?

    Thanks,
    Sam Lester (MSFT)


    https://blogs.msdn.microsoft.com/samlester/

    Twitter - @SQLSamLester

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Wednesday, February 1, 2017 8:14 AM
    Moderator
  • Hello Naman,

    Is there any chance that your SQL Server instances are x64 and the SP2 you downloaded is x86?


    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Wednesday, February 1, 2017 8:24 AM
  • Hi Sam,

    Thanks for the reply.

    It's 64 bit architecture.

    I was able to select shared features and applied SP2 for them.

    cannot place snapshot here due to more than 6000 characters.


    Regards, Naman

    Wednesday, February 1, 2017 8:25 AM

  • Regards, Naman

    Wednesday, February 1, 2017 8:27 AM
  • Sam's reply wasn't there when I expanded this question, sorry for the redundancy.

    http://ekremonsoy.blogspot.com | http://www.ekremonsoy.com | @EkremOnsoy

    Wednesday, February 1, 2017 8:28 AM
  • File itself shows architecture.

    SQLServer2014SP2-KB3171021-x64-ENU


    Regards, Naman

    Wednesday, February 1, 2017 8:29 AM

  • Regards, Naman

    Wednesday, February 1, 2017 8:35 AM
  • Hi Naman,

    Can you check the current version level of each SQL instance on those 11 instances? You can use below query to verify that.

    Select SERVERPROPERTY('ProductVersion')

    Build Number of those instances should be less than 12.0.5000.0

    Thanks,


    Kindly mark the reply as answer if they help

    Wednesday, February 1, 2017 8:43 AM
  • Can you try running it from the command prompt with the /allinstances flag (or with a single instance name to see if it runs successfully)?

    https://technet.microsoft.com/en-us/library/dd638066(v=sql.120).aspx

    Thanks,
    Sam Lester (MSFT)


    https://blogs.msdn.microsoft.com/samlester/

    Twitter - @SQLSamLester

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Wednesday, February 1, 2017 8:44 AM
    Moderator
  • they are as following.

    12.0.4439.1
    12.0.4439.1
    12.0.4439.1
    11.0.6567.0
    12.0.2000.8
    12.0.4439.1
    12.0.4439.1
    10.50.6529.0
    12.0.4439.1
    12.0.4439.1
    11.0.6567.0


    Regards, Naman

    Thursday, February 2, 2017 4:34 AM
  • I tried following.

    D:\Temp\SQL2014\SP2\SQLServer2014SP2-KB3171021-x64-ENU.exe /AllInstances /action=Patch /IAcceptSQLServerLicenseTerms

    but still no luck.


    Regards, Naman

    Thursday, February 2, 2017 5:14 AM
  • they are as following.

    12.0.4439.1
    12.0.4439.1
    12.0.4439.1
    11.0.6567.0
    12.0.2000.8
    12.0.4439.1
    12.0.4439.1
    10.50.6529.0
    12.0.4439.1
    12.0.4439.1
    11.0.6567.0


    Regards, Naman

    Hi Naman,

    So they all are not SQL Server 2014.

    12.0.4439.1 - SQL Server 2014 SP1 CU5 
    12.0.4439.1 - SQL Server 2014 SP1 CU5 
    12.0.4439.1 - SQL Server 2014 SP1 CU5 
    11.0.6567.0 - SQL Server 2012 SP3 CU6 
    12.0.2000.8 - SQL Server 2014 RTM 
    12.0.4439.1 - SQL Server 2014 SP1 CU5 
    12.0.4439.1 - SQL Server 2014 SP1 CU5 
    10.50.6529.0 - SQL Server 2008 R2 SP3
    12.0.4439.1  - SQL Server 2014 SP1 CU5 
    12.0.4439.1  - SQL Server 2014 SP1 CU5 
    11.0.6567.0  - SQL Server 2012 SP3 CU6 

    But still it should at least allow you to select 8 such instances which qualify for this update you trying to apply.

    Can you paste screen shot pls?

    Thanks,


    Kindly mark the reply as answer if they help

    Thursday, February 2, 2017 7:28 AM
  • yes, you can exclude them. but they all are running on same box. SQL 2008 R2, SQL 2012 and SQL 2014.

    Regards, Naman

    Thursday, February 2, 2017 8:03 AM
  • and patch picks up only SQL 2014 when we apply sql 2014 sp2.

    Regards, Naman

    Thursday, February 2, 2017 8:04 AM
  • So what's the question at this point? Are you able to patch your 2014 instances with SP2? Or is it still not recognizing them as "patch-able"?

    Are the instances 32-bit?

    Can you please provide the output from the following query for one of the 2014 instances?

    select @@version

    And can you also post the discovery report OR the information from summary.txt from when you ran with /allinstances from the command line?

    Thanks,
    Sam Lester (MSFT)


    https://blogs.msdn.microsoft.com/samlester/

    Twitter - @SQLSamLester

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Thursday, February 2, 2017 9:19 AM
    Moderator
  • Question is when I run patch SQL 2014 SP2, I am not able to select any single SQL 2014 instance and patch cannot proceed even though I am trying to apply correct 64-bit patch and current all instances running on SQL 2014 SP1+CU5.

    Why am I not able to select instances?


    Regards, Naman

    Monday, February 6, 2017 3:22 AM
  • Please provide the requested info from above (discovery report, summary.txt, and results from 'SELECT @@VERSION') so we can get more details about the instances. We need to see what SQL Server setup is detecting in order to help out.

    Thanks,
    Sam Lester (MSFT)


    https://blogs.msdn.microsoft.com/samlester/

    Twitter - @SQLSamLester

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Monday, February 6, 2017 8:35 AM
    Moderator
  • Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2012 (SP3-CU6-GDR) (KB3194724) - 11.0.6567.0 (X64)
     Oct 10 2016 18:45:52
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
     Feb 20 2014 20:04:26
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2014 (SP1-CU5) (KB3130926) - 12.0.4439.1 (X64)
     Feb 15 2016 12:12:43
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2012 (SP3-CU6-GDR) (KB3194724) - 11.0.6567.0 (X64)
     Oct 10 2016 18:45:52
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

    Microsoft SQL Server 2008 R2 (SP3) - 10.50.6529.0 (X64)
     Mar 19 2015 13:19:13
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)


    Regards, Naman

    Tuesday, February 7, 2017 1:34 AM
  • Thanks for posting the details. Can you try the command line against a single instance of 2014? Earlier you had listed the command line syntax using /ALLINSTANCES. This time, can you try with a single instance?

    Ex:

    D:\Temp\SQL2014\SP2\SQLServer2014SP2-KB3171021-x64-ENU.exe /action=Patch /IAcceptSQLServerLicenseTerms /InstanceID=<Machine\Instance>

    Thanks,
    Sam Lester (MSFT)


    https://blogs.msdn.microsoft.com/samlester/

    Twitter - @SQLSamLester

    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    Tuesday, February 7, 2017 12:42 PM
    Moderator
  • Hi Sam,

    I did try again but I am still not able to select the instance which I put with instanceid.

    any other option?


    Regards, Naman

    Thursday, February 9, 2017 8:39 AM
  • Hi Nik,

    I’m just wondering what does the feature discovery report say, does the result different from the result of  SELECT @@VERSION? I’m asking this because:

    During my test, it seems that the installer does only take version number from registry(same as feature discovery report), not from SELECT @@VERSION. So if the registry is in an inconsistent state, the installer might recognize the instances incorrectly.

    If you have any other questions, please let me know.

    Regards,
    Lin

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, February 16, 2017 5:23 AM
    Moderator
  • I think it is due to missing cache MSI file which resides in %windir%\Installer; eg: C:\Windows\Installer.

    You must try this.

    https://social.msdn.microsoft.com/Forums/en-US/4b7cce6e-df1c-4d6c-b3c0-154a86286bad/select-instance-is-not-available-when-upgrade-to-sql-2008-r2?forum=sqlsetupandupgrade

    https://social.msdn.microsoft.com/Forums/en-US/fb96fc80-f6ee-4bac-90d4-35fccf913fbf/select-instance-page-missing-when-i-try-to-upgrade-sql-2008-sp1-to-sql-2008-r2?forum=sqlsetupandupgrade

    Saturday, February 18, 2017 8:47 AM