none
Upgrade SQL Server 2008 R2 RTM Developer X64 to SQL Server 2012 RTM Developer X64 fails

    Question

  • ---------------------------
    Rule Check Result
    ---------------------------
    Rule "SQL Server 2012 Feature Upgrade" failed.

    The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
    ---------------------------
    OK   
    ---------------------------

    My upgrade in supported upgrade scenarios. Why I am receiving this error ?

    More information:

    select @@version;

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    =============================================

    However in log  setup picks up standard ( from where ? )  :

    C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120412_090305\Detail.txt

    ==================================

    (14) 2012-04-12 09:27:25 Slp: Initializing rule      : SQL Server 2012 Feature Upgrade
    (14) 2012-04-12 09:27:25 Slp: Rule is will be executed  : True
    (14) 2012-04-12 09:27:25 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
    (14) 2012-04-12 09:27:25 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
    (14) 2012-04-12 09:27:25 Slp: -- SkuUpgradeRule : Found feature package  'sql_as_ctp6_Cpu64' with SkuValue=STANDARD (Standard) ProductVersion=10.50.1600.1
    (14) 2012-04-12 09:27:25 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition STANDARD for feature package 'sql_as_Cpu64'.
    (14) 2012-04-12 09:27:25 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=STANDARD (Standard) sourceArchitecture=X64 targetEdition=DEVELOPER (Developer) targetArchitecture=X64
    (14) 2012-04-12 09:27:25 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
    (14) 2012-04-12 09:27:25 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
    (14) 2012-04-12 09:27:25 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
    (14) 2012-04-12 09:27:25 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
    (14) 2012-04-12 09:27:25 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
    (14) 2012-04-12 09:27:25 Slp: Rule running on machine: SYD-WMSM-1
    (14) 2012-04-12 09:27:25 Slp: Rule evaluation done   : Failed
    (14) 2012-04-12 09:27:25 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
    (14) 2012-04-12 09:27:25 Slp: Send result to channel : RulesEngineNotificationChannel
    (14) 2012-04-12 09:27:25 Slp: Initializing rule      : Incomplete upgrade




    • Edited by MSMit Thursday, April 12, 2012 7:38 AM
    Thursday, April 12, 2012 12:49 AM

All replies

  • Hello,

    Please run the discovery report and make sure you only have Developer Edition installed.

    http://blogs.msdn.com/b/petersad/archive/2009/11/13/sql-server-2008-discovery-report.aspx  

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Thursday, April 12, 2012 2:29 AM
  • In fact, according to summary.txt  , there is a certain mixture of standard and developer.  I remember failing standard 2008 R2 setup upgrade a year ago, then I seem to have reinstalled developer from scratch. Is there any chance for upgrade path yet ? I expected installer to be more intelligent and pick up Database Engine Services other than anything else.

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
      SQL Server 2008 R2   MSSQLSERVER.INACTIVE MSAS10_50.MSSQLSERVER          Analysis Services                        1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      10.3.5500.0     No        
      SQL Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                   1033                 Express Edition      10.3.5500.0     No        
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Management Tools - Basic                 1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008 R2                                                       Management Tools - Complete              1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools Connectivity                1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools Backwards Compatibility     1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools SDK                         1033                 Standard Edition     10.50.1600.1    No        
      SQL Server 2008 R2                                                       Integration Services                     1033                 Standard Edition     10.50.1600.1    No        

    Thursday, April 12, 2012 2:49 AM
  •  

    Hello,

    Remove the Standard Components from your computer if you are not using them. Reinstall them from the Developer Edition media, then try to perform the upgrade again.

    Do you agree with this approach?

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Thursday, April 12, 2012 3:34 AM
  • I followed remove/reinstall path for developer 2008 R2

    NOW

    ---------------------------
    Rule Check Result
    ---------------------------
    Rule "SQL Server 2008 R2 Service Pack 1 or later is required for upgrade." failed.

    The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2012 are not at the required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
    ---------------------------
    OK   
    ---------------------------

    KJRTMUpgradeBlockRule Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack.   X failed

    =========================

    All that despite

    select @@version;

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    Attempt to re-install SP1

    running SQLServer2008R2SP1-KB2528583-x64-ENU.exe

    resulted

    TITLE: SQL Server Setup failure.
    ------------------------------

    SQL Server Setup has encountered the following error:


    A failure was detected for a previous installation, patch, or repair during configuration for features [SQL_PowerShell_Engine_CNS,SQL_PowerShell_Tools_ANS,]. In order to apply this patch package (KB2528583), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.

    Error code 0x84B20001.

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    Yes, I had a problem with PowerShell when re-installing SQL Server Developer 2008 R2 ( this bit failed ) , which I have no idea how to fix. I am on Windows 7 Enterprise with PowerShell 2 built-in. I suspect backing up databases and wiping everything out  takes less time in general , than trying to upgrade.

    Thursday, April 12, 2012 5:13 AM
  • So did you upgrade SQL Server 2008 to SP2 as advised in the log?

    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Jeff Wharton
    MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCSD, MCITP, MCDBA
    Blog: Mr. Wharty's Ramblings
    Twitter: @Mr_Wharty
    MC ID: Microsoft Transcript

    Thursday, April 12, 2012 5:27 AM
  • Nothing to do, so  I decided to repair 2008 R2 Developer

    It is becoming amusing.  Have a look at the error. Why on earth for X64   SSCERuntime_x86-ENU.msi is expected.  ( there is SSCERuntime.msi there )

    TITLE: SQL Server 2008 R2 Setup
    ------------------------------

    The following error has occurred:

    Error 1316.A network error occurred while attempting to read from the file C:\SQL_2008_R2\1033_ENU_LP\x64\setup\SSCERuntime_x86-ENU.msi

    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0&EvtType=0xDF039760%25401201%25401

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    no termination though and finally again


    TITLE: SQL Server 2008 R2 Setup
    ------------------------------

    The following error has occurred:

    Setup failed to install Windows PowerShell. Error code is -2145124329

    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0&EvtType=0x82728477%25400x237CA5E1%25401215%25400

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    Not surprisingly no additional info if follow the link above.




    • Edited by MSMit Thursday, April 12, 2012 5:37 AM
    Thursday, April 12, 2012 5:34 AM
  • > So did you upgrade SQL Server 2008 to SP2 as advised in the log?

    You may have noticed that I am dealing with SQL Server 2008 R2 upgrade . My understanding that a programmer who wrote this bit of installer just copied and pasted the same text as for SQL Server 2008. My problems with SP1 for 2008 R2 I've already described.

    Thursday, April 12, 2012 5:49 AM
  • I wonder if it's complaining about the Express Edition and getting a little confused about what versions of 2008/2008 R2 it thinks are installed

     SQL Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      10.3.5500.0     No       


    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Jeff Wharton
    MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCSD, MCITP, MCDBA
    Blog: Mr. Wharty's Ramblings
    Twitter: @Mr_Wharty
    MC ID: Microsoft Transcript

    Thursday, April 12, 2012 5:56 AM
  • > I wonder if it's complaining about the Express Edition

    No, for the moment there is NO Express Edition at all. I wiped it out. There is semi-clean  but quite functional Developer 2008 R2.  Quite functional because everything  I need works. Semi-clean because I never bothered to resolve Powershell failure. Now this failure(most likely)  prevents to apply SP1  which in turn stops the upgrade to 2012.

    Thursday, April 12, 2012 6:05 AM
  • So I wonder why summary.txt shows Express Edition as installed?

    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Jeff Wharton
    MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCSD, MCITP, MCDBA
    Blog: Mr. Wharty's Ramblings
    Twitter: @Mr_Wharty
    MC ID: Microsoft Transcript

    Thursday, April 12, 2012 6:06 AM
  • >So I wonder why summary.txt shows Express Edition as installed?

    Not anymore. That's what I started with.  Then independently I followed Alberto's advice in this thread.

    Summary.txt now

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Management Tools - Basic                 1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Management Tools - Complete              1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools Connectivity                1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools Backwards Compatibility     1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Client Tools SDK                         1033                 Developer Edition    10.50.1600.1    No        
      SQL Server 2008 R2                                                       Integration Services                     1033                 Developer Edition    10.50.1600.1    No       

    Thursday, April 12, 2012 6:16 AM
  • The Database Engine Version number (10.50.1600.1) does not match the version number of SP1.  It should be 10.50.2500.

    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

    Jeff Wharton
    MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt), MCT, MCPD, MCSD, MCITP, MCDBA
    Blog: Mr. Wharty's Ramblings
    Twitter: @Mr_Wharty
    MC ID: Microsoft Transcript

    Thursday, April 12, 2012 6:21 AM
  • >The Database Engine Version number (10.50.1600.1) does not match the version number of SP1.  It should be 10.50.2500.

    I know that. Didn't I describe my problem with SP1 in this thread before ?

    Thursday, April 12, 2012 6:29 AM