Our server is running Windows 2008 Standard Edition x64 with SP2. We are attempting an upgrade from our SQL 2005 Standard Edition 64bit (we assume) to SQL 2012 64bit. When trying to use the upgrade wizard, it does NOT find the instance or any features. Attempted same upgrade with command prompt syntax and received the following error:
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.
The summary.txt file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2067922429
Exit facility code: 1214
Exit error code: 515
Exit 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.
Start time: 2012-09-27 14:30:19
End time: 2012-09-27 14:31:12
Requested action: Upgrade
Machine Properties:
Machine name: APPSERVER
Machine processor count: 4
OS version: Windows Server 2008
OS service pack: Service Pack 2
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2005 MSSQLSERVER MSSQL.1
Database Engine Services 1033 Standard Edition
9.4.5057 No
SQL Server 2005 MSSQLSERVER MSSQL.1
SQL Server Replication 1033 Standard Edition
9.4.5057 No
SQL Server 2005 MSSQLSERVER MSSQL.1
Full-Text and Semantic Extractions for Search 1033 Standard Edition 9.4.5057 No
SQL Server 2005 MSSQLSERVER MSSQL.1
SharedTools 1033
Standard Edition 9.4.5057 No
SQL Server 2005 MSSQLSERVER MSSQL.2
Analysis Services 1033
Standard Edition 9.4.5057 No
SQL Server 2005
Tools 1033
Standard Edition 9.4.5057 No
SQL Server 2005
ToolsClient 1033
Standard Edition 9.4.5057 No
SQL Server 2005
ToolsClient\Connectivity 1033 Standard Edition
9.4.5057 No
SQL Server 2005
ToolsDocument 1033
Standard Edition 9.4.5057 No
SQL Server 2005
ToolsDocument\BOL 1033
Standard Edition 9.4.5057 No
SQL Server 2005
NS 1033
Standard Edition 9.4.5057 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\Administrator.OCSO\Desktop\SQL 2012\x64\setup\
Installation edition: Standard
Product Update Status:
None discovered.
User Input Settings:
ACTION: Upgrade
AGTDOMAINGROUP: <empty>
ALLOWUPGRADEFORSSRSSHAREPOINTMODE: false
CONFIGURATIONFILE:
ENU: true
ERRORREPORTING: false
FAILOVERCLUSTERROLLOWNERSHIP: 2
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
FTUPGRADEOPTION: Import
HELP: false
INDICATEPROGRESS: false
INSTANCEID: MSSQL.1
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Authority\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
PID: *****
QUIET: true
QUIETSIMPLE: false
RSCATALOGSERVERINSTANCENAME: Unknown
RSUPGRADEDATABASEACCOUNT: administrator
RSUPGRADEPASSWORD: *****
SQMREPORTING: false
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120927_142920\ConfigurationFile.ini
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120927_142920\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngineRuleFailureException
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.
HResult : 0x84be0203
FacilityCode : 1214 (4be)
ErrorCode : 515 (0203)
Data:
SQL.Setup.FailureCategory = RuleViolationFailure
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.RulesEngineExtension.RunRulesAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
y.txt file is:
Any suggestions would be greatly appreciated.