Quantcast
Channel: Forum SQL Server Setup & Upgrade
Viewing all articles
Browse latest Browse all 7532

Upgrading from 2005 to 2008, setup does not detect existing installation

$
0
0

I've got an x64 Standard install of 2005, I'm trying to upgrade to x64 Standard 2008. When I run the upgrade I get the error "There are no features selected for upgrade". When I look at the log, it seems that the existing installation is not being detected:

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:                    2012-10-04 16:19:18
  End time:                      2012-10-04 16:21:58
  Requested action:              Upgrade

Machine Properties:
  Machine name:                  COMPUTER1
  Machine processor count:       2
  OS version:                    Windows Server 2008
  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

Package properties:
  Description:                   SQL Server Database Services 2008
  SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
  ProductName:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         D:\x64\setup\
  Installation edition:          STANDARD

User Input Settings:
  ACTION:                        Upgrade
  AGTDOMAINGROUP:                <empty>
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:            
  ERRORREPORTING:                False
  FAILOVERCLUSTERROLLOWNERSHIP:  2
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 *****
  FTUPGRADEOPTION:               Import
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  MEDIASOURCE:                   D:\
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  RSCATALOGSERVERINSTANCENAME:   Unknown
  RSUPGRADEDATABASEACCOUNT:     
  RSUPGRADEPASSWORD:             *****
  SQLDOMAINGROUP:                <empty>
  SQMREPORTING:                  False
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121004_161622\ConfigurationFile.ini

Detailed results:

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121004_161622\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.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

I have no idea why this is happening, can anyone shed some light on this? The version of 2005 is 9.00.4053.00, which I believe is SP3.


Viewing all articles
Browse latest Browse all 7532

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>