Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I have a test environment set up with the following:

  • Virtual Machine (Hyper-V)
  • Windows Server 2008 R2 SP1(x64-bit)
  • Windows SQL Server 2005 Developer Edition SP4 (x64-bit)(default instance name)
    • 1 Database with Merge Replication set up... 3 publications with 2 subscribers each.

We are testing the procedure for upgrading to SQL Server 2012 Developer Edition (sp1)...

I have downloaded the iso for 64bit SQL Server 2012 Dev. (sp1) from MSDN (full licensed copy) and have started going down the upgrade path. At one of the final stages, where it begins a check for different criteria, we run into a bizarre issue as outlined below:

Rule "Upgrade architecture mismatch" failed. The CPU architectures of upgrading feature(s) are different. To upgrade these features, Setup architecture must be the same as the features being installed.

Furthermore, in the upgrade log file, I found the following (more verbose) output:

(03) 2012-12-28 14:02:45 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.BlockMixedArchitecture
(03) 2012-12-28 14:02:45 Slp: Rule 'BlockMixedArchitectureUpgrade' detection result: IsMixedArchitectureInstall= True 
(03) 2012-12-28 14:02:45 Slp: Evaluating rule        : BlockMixedArchitectureUpgrade
(03) 2012-12-28 14:02:45 Slp: Rule running on machine: REPLICATIONTEST
(03) 2012-12-28 14:02:45 Slp: Rule evaluation done   : Failed
(03) 2012-12-28 14:02:45 Slp: Rule evaluation message: The CPU architectures of upgrading feature(s) and this installation program are different. To upgrade these features, Setup architecture must be the same as the features being installed.

I have made sure that we are on an x64 system and not an ia64 and I see no reason why a mismatch would be occurring. Something to note: We cannot simply install SQL Server 2012, and reattach the databases to it as we have over 20 live databases (in production) with over 40 publications set up... this would be an absolute nightmare if we had to re-set up replication.


Here is the version info for the SQL Server 2005 setup:

Microsoft SQL Server 2005 - 9.00.5000.00 (X64) 
Dec 10 2010 10:38:40 
Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

9.00.5000.00 indicated SP4.


I will be calling Microsoft support about this tomorrow.

share|improve this question
    
Can you verify the edition you downloaded? Is it possible you downloaded the Standard edition of SQL 2012, and not the Developer edition? –  SQLRockstar Dec 28 '12 at 22:47
1  
Can you run "select @@version" on the current instance and post the entire output. –  mrdenny Dec 28 '12 at 22:51
2  
The amount of MVP and MCMs responding to this is outstanding! Looks like someone on the MSDN forums ran into the same issue: social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/… –  Ali Razeghi Dec 28 '12 at 23:22
2  
Could either tools (SSMS etc) or SSIS have been installed separately to the main install as 32bit? –  Mark Storey-Smith Dec 31 '12 at 11:23
1  
Very kind @WesCrockett, thank you. –  Mark Storey-Smith Dec 31 '12 at 17:59
show 10 more comments

1 Answer

up vote 4 down vote accepted
+100

Could either tools (SSMS etc) or SSIS have been installed separately to the main install as 32bit?

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.