When he clicked OK on the above dialog, a new error appeared at the bottom of the "Select Features" page. I proceeded to view SQL Server setup log and found the following: Overall summary: Final result: User cancelled Exit code (Decimal): -2068380094 Exit facility code: 1207 Exit error code: 1602 Exit message: User has cancelled.
Start time: 2011-08-26 End time: 2011-08-26 Requested action: Upgrade Machine Properties: Machine name: DENVER Machine processor count: 2 OS version: Windows 7 OS service pack: Service Pack 1 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 NR2007 MSSQL.2 Database Engine Services 1033 Express Edition 9.4.5000 No Sql Server 2005 NR2007 MSSQL.2 Shared Tools 1033 Express Edition 9.4.5000 No Sql Server 2005 SQLEXPRESS MSSQL.3 Database Engine Services 1033 Express Edition 9.4.5000 No Sql Server 2005 SQLEXPRESS MSSQL.3 Shared Tools 1033 Express Edition 9.4.5000 No Sql Server 2005 Tools 1033 Express Edition 9.4.5000 No Sql Server 2005 Tools Client 1033 Express Edition 9.4.5000 No Sql Server 2005 Tools Client\Connectivity 1033 Express Edition 9.4.5000 No Sql Server 2008 R2 Management Tools - Basic 1033 Express Edition .1 No Package properties: Description: SQL Server Database Services 2008 R2 Product Name: SQL Server 2008 R2 Type: RTM Version: 10 SPLevel: 0 Installation location: y:d9eb6bef166b4e8a3f4a0462acf\x64\setup\ Installation edition: EXPRESS User Input Settings: ACTION: Upgrade AGTDOMAINGROUP: ISSVCACCOUNT: NT AUTHORITY\Network Service ISSVCPASSWORD: ***** ISSVCSTARTUPTYPE: Automatic PASSPHRASE: ***** PCUSOURCE: PID: ***** QUIET: False QUIETSIMPLE: False RSCATALOGSERVERINSTANCENAME: Unknown RSUPGRADEDATABASEACCOUNT: RSUPGRADEPASSWORD: ***** SQLDOMAINGROUP: SQMREPORTING: True UIMODE: Auto Advance X86: False Configuration file: C:\Program Files\Microsoft SQL Server0\Setup Bootstrap\Log110826_174309\Configuration Detailed results: Rules with failures: Global rules: Scenario specific rules: Rules report file: C:\Program Files\Microsoft SQL Server0\Setup Bootstrap\Log110826_174309\System Configuration Check_Exception summary: The following is an exception stack listing the exceptions in outermost to innermost order Inner exceptions are being indented Exception type: Microsoft.
Initially I tried to resolve the issue by adding his Windows account as a user in the msdb database and then assigning the account under db_ssadmin role. Next he was made a db_owner in the msdb database, this did not help either. Promptly rolling back his elevated permissions, I decided to look at the Windows side of things.
Going against all security best practices and knowing I was committing a cardinal sin, I assigned his account to the sysadmin server role. Once his Windows AD account was added as a local Administrator in the development box, things looked okay.
I did not want him to be an administrator even in a development box, so I started to look at the error message closely and tried to make some sense of it.
When he ran setup, he chose "Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008" on SQL Server Installation Center and then follow instructions.
Execute(String action Id, Text Writer error Stream) at Microsoft.
Setup cannot upgrade from 32-bit platform to 64-bit platform: cross-platform upgrade is not supported.
Accelerate application lifecycles and improve application quality of service by consolidating your SQL Servers on the private cloud with VMware v Sphere.
With v Sphere, you can consolidate your SQL infrastructure by 4X to 20X and cut hardware and software costs by more than 50 percent while avoiding the painful compromises associated with traditional database consolidation.