dbTalk Databases Forums  

Upgrade from SQL Server 2005 to 2008 failed

microsoft.public.sqlserver.setup microsoft.public.sqlserver.setup


Discuss Upgrade from SQL Server 2005 to 2008 failed in the microsoft.public.sqlserver.setup forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ralph
 
Posts: n/a

Default Upgrade from SQL Server 2005 to 2008 failed - 09-08-2009 , 03:51 AM






Hello,
I tried to upgrade our SQL-Server. I used the upgrade advisor first and it
reported no problems. There was only one warning that the installation on a
DC is not recommended. But the 2005 version runs on the server for over two
years and there was no problem. So I startet the installation. The setup
program has found the instance. In the selct features step all installed
features where found and marked up. The setup process ran through very
quickly and I cannot remember that there was any failure or problem reportet.
After the installation i wondered, where the new SQL-Server is. In the start
menu I could only find the upgrade advisor an the installation center.

I tried again to run the setup, but now I have the problem, that the "Select
Features"-List is empty and the setup cannot be continued.

I have found the following kb article, but it did not help me.
http://support.microsoft.com/kb/955399

This article describes how to locate the summary log file.
I have three ! log files from the same installation which where created with
only some seconds difference:
20090907_185808
20090907_185820
20090907_185900

I tried to locate the Final Result entry but I could not find something what
seems to be important. I cannot find the Configuration File which is
mentioned.

This is the complete contents of the file, you can also find the system
information:

---------------------------------------------------------------------------------------

Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2009-09-07 18:59:03
End time: 2009-09-07 19:00:25
Requested action: RunRules

Machine Properties:
Machine name: FDBASERVER
Machine processor count: 4
OS version: Windows Server 2003
OS service pack: Service Pack 2
OS region: Deutschland
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 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005 MSSQLSERVER MSSQL.1
SQL Server Replication 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005 MSSQLSERVER MSSQL.1
Full-Text Search 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005 MSSQLSERVER MSSQL.1
SharedTools 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005 MSSQLSERVER MSSQL.2
Analysis Services 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
DTS 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
Tools 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
ToolsClient 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
ToolsClient\Connectivity 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
ToolsDocument 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
ToolsDocument\BOL 1031 Standard
Edition 9.00.1399.06 No
Sql Server 2005
NS 1031 Standard
Edition 9.00.1399.06 No

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

User Input Settings:
ACTION: RunRules
CONFIGURATIONFILE:
FEATURES:
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
MEDIASOURCE: E:\
QUIET: False
QUIETSIMPLE: False
RULES:
GLOBALRULES,SqlUnsupportedProductBlocker,PerfMonCo unterNotCorruptedCheck,Bids2005InstalledCheck,Bloc kInstallSxS,AclPermissionsFacet,FacetDomainControl lerCheck,SSMS_IsInternetConnected,FacetWOW64Platfo rmCheck,FacetPowerShellCheck
X86: False

Configuration file: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20090907_185900\ConfigurationFile.in i

Detailed results:

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file: C:\Program Files\Microsoft SQL
Server\100\Setup
Bootstrap\Log\20090907_185900\SystemConfigurationC heck_Report.htm


---------------------------------------------------------------------------------------




I ran the uninstall as mentioned in the kb article. But the deinstallation
failed with the message:

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.Setup.Chainer.Workflow.NoopWor kflowException
Message:
No feature were uninstalled during the setup execution. The
requested features may not be installed. Please review the summary.txt logs
for further details.

I also tried it without the /q and without /instanceid and also without
/feature as well as different combinations. But I had no luck.

Can anybody help me to solve this problem ? I have already installed the
SQL-server in a VM and did a restore of the backap files. The database has
been restored correctly and the tests worked. So I know I also can do an new
installation and restore the databases. But I want to prevent that I have to
do all the settings again. If the Database does not work on the next day, I
have the problem that many colleagues cannot work. But if there is no
solution with the upgrade problem I want to know if it is better to install
SQL Srv 2008 parallel to the SQL Svr 2005 and the import the files and
uninstall the SQL SRV 2005. Or would it be better to do backups, uninstall
SQL Srv 2005 and then install the Svr 2008 and do a recovery ?

Many thanks in advance.

Ralph

Reply With Quote
  #2  
Old   
Ralph
 
Posts: n/a

Default RE: Upgrade from SQL Server 2005 to 2008 failed - 09-08-2009 , 03:58 AM






Hello again,

I have forgotten to mention that the edition mentioned in the logfile is
wrong. I did not choose to install the EVAL edition. I have entered a valid
product code of the standard edition.
The code was accepted and the installation script continued.

Ralph

Reply With Quote
  #3  
Old   
Erland Sommarskog
 
Posts: n/a

Default Re: Upgrade from SQL Server 2005 to 2008 failed - 09-08-2009 , 04:58 PM



Ralph (Ralph (AT) discussions (DOT) microsoft.com) writes:
Quote:
I tried to upgrade our SQL-Server. I used the upgrade advisor first and
it reported no problems. There was only one warning that the
installation on a DC is not recommended. But the 2005 version runs on
the server for over two years and there was no problem. So I startet the
installation. The setup program has found the instance. In the selct
features step all installed features where found and marked up. The
setup process ran through very quickly and I cannot remember that there
was any failure or problem reportet. After the installation i wondered,
where the new SQL-Server is. In the start menu I could only find the
upgrade advisor an the installation center.
Beware that there will be a new program group for SQL 20008.

If you do

SQLCMD

what happens? Is anyone responding? If there is, what does "SELECT
@@version" report?

Quote:
Sql Server 2005 MSSQLSERVER MSSQL.1
Database Engine Services 1031 Standard
Edition 9.00.1399.06 No
I note that this is the RTM version of SQL 2005. I guess that Setup
should have barfed if this upgrade is not supported. But it's never
bad to install a service pack everyonce in a while.

Quote:
Can anybody help me to solve this problem ? I have already installed the
SQL-server in a VM and did a restore of the backap files. The database
has been restored correctly and the tests worked. So I know I also can
do an new installation and restore the databases. But I want to prevent
that I have to do all the settings again. If the Database does not work
on the next day, I have the problem that many colleagues cannot work.
But if there is no solution with the upgrade problem I want to know if
it is better to install SQL Srv 2008 parallel to the SQL Svr 2005 and
the import the files and uninstall the SQL SRV 2005. Or would it be
better to do backups, uninstall SQL Srv 2005 and then install the Svr
2008 and do a recovery ?
If you need this working in the morning, making a new install on a new
VM, or a named instance is probably a faster path than trying to get
the upgrade in order.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.