May 21, 2010 at 2:04 am
Morning
Having real trouble upgrading my Eval 2008r2 to Developer. It says it works, everything is okay, but doesn't seem to have done it. Here's the Log after the upgrade
Overall summary:
Final result: Pending
Exit code (Decimal): 0
Exit message: Pending
Start time: 2010-05-21 08:49:37
End time: 2010-05-21 08:51:43
Requested action: EditionUpgrade
Machine Properties:
Machine name: XXX-XXX-NN
Machine processor count: 4
OS version: Windows Server 2003
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 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Management Tools - Basic 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Management Tools - Complete 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools Connectivity 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools Backwards Compatibility 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Client Tools SDK 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Sql Server 2008 R2 Integration Services 1033 Enterprise Evaluation Edition 10.50.1352.12 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: W:\Server Applications\SQL Server\2008r2dev\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: EditionUpgrade
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100521_084916\ConfigurationFile.ini
ENU: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SNAC_SDK,OCS,CE_RUNTIME,SNAC,DSO,BCREDIST
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTANCENAME: MSSQLSERVER
PASSPHRASE: *****
PID: *****
QUIET: False
QUIETSIMPLE: False
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100521_084916\ConfigurationFile.ini
Detailed results:
Feature: SQL Client Connectivity
Status: Skipped
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Skipped
MSI status: Passed
Configuration status: Passed
Feature: SQL Compact Edition Runtime
Status: Skipped
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Skipped
MSI status: Passed
Configuration status: Passed
Feature: Microsoft SQL Server 2005 Backward compatibility
Status: Skipped
MSI status: Passed
Configuration status: Passed
Feature: Decision Support Objects (DSO)
Status: Skipped
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100521_084916\SystemConfigurationCheck_Report.htm
Any ideas? I don't want to lose all my work when the 180days is up...
ta
pete
May 21, 2010 at 2:49 am
I think that this:
IACCEPTSQLSERVERLICENSETERMS: False
is the source of your trouble...
Can you send the output of this script:
SELECT
SERVERPROPERTY('ProductVersion') AS ProductVersion,
SERVERPROPERTY('ProductLevel') AS ProductLevel,
SERVERPROPERTY('Edition') AS Edition,
SERVERPROPERTY('EngineEdition') AS EngineEdition;
May 21, 2010 at 2:52 am
Hi - here you go...
ProductVersion10.50.1352.12
ProductLevelCTP
Edition Enterprise Evaluation Edition (64-bit)
EngineEdition 3
ta
pete
May 21, 2010 at 3:06 am
I dont think that you can upgrade , backup your database , do a side by side install and restore your database into that.
May 21, 2010 at 3:13 am
Oh poo. No way of upgrading at all? It's not hidden in the registry is it?
pete
May 21, 2010 at 3:24 am
Dave Ballantyne (5/21/2010)
I dont think that you can upgrade , backup your database , do a side by side install and restore your database into that.
David, BOL says that "enterprise eval" to "developer" is a supported upgrade path...Am I missing something?
(However I agree with you, it is easier to install the dev edition...)
May 21, 2010 at 3:35 am
Although , at the back of my mind , i didnt think i could be done, i could well be wrong 🙂
If BOL states its supported ,then it is.
Right now though this installation seems to be in an indeterminate state, the user has upgraded , seemed to of worked , but sqlserver still has the old version.
Its to dangerous to go tinkering with sqlserver to convince it that it is now a developer edition version. All hell could really break loose.
Play safe , do a fresh install and use that.
May 21, 2010 at 3:50 am
Oh i don't mind doing that, as the r2 is a test box, so there's not much on there.
But I can't be the only one trying to upgrade - and I don't remember seeing a new parameter during the eval install process.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply