Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SQL2000 to SQL2008 in-place upgrade failing

Posted on 2010-11-24
5
1,161 Views
Last Modified: 2012-05-10
I am trying to do an in place SQL 2000 to SQL 2008 upgrade but it keeps on failing when the feature selection appears. From what I can see the error stems from me trying to upgrade from 2000 Developer Edition to 2008 Enterprise Edition.

I need to overcome this problem. Ideas anyone, please?

Errors in the log

20010-11-24 14:44:20 Slp: Running Action: PostMsiTimingConfigAction
2010-11-24 14:44:20 Slp: The object state property 'workflow' is null/empty.
2010-11-24 14:44:20 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution.
2010-11-24 14:44:20 Slp: Completed Action: PostMsiTimingConfigAction, returned False
2010-11-24 14:44:20 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Running Action: ExecuteCloseWorkflow
2010-11-24 14:44:20 Slp: Workflow to execute: 'CLOSE'
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Skipping Action: ProduceStatusLogs
2010-11-24 14:44:20 Slp: Action is being skipped due to the following restrictions:
2010-11-24 14:44:20 Slp: Condition "Is the datastore flag /Scenario/GlobalFlags/AreProductFeaturesSupported set" did not pass as it returned false and true was expected.
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Running Action: FinalizeProgressStatus
2010-11-24 14:44:20 Slp: Completed Action: FinalizeProgressStatus, returned True
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Running Action: RebootMessageAction
2010-11-24 14:44:20 Slp: Completed Action: RebootMessageAction, returned True
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Skipping Action: FinishPage
2010-11-24 14:44:20 Slp: Action is being skipped due to the following restrictions:
2010-11-24 14:44:20 Slp: Condition "Is the user's scenario set to EditionUpgrade" did not pass as it returned false and true was expected.
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Skipping property RequireMode of class: StopAction
2010-11-24 14:44:20 Slp: Input of property will not be set due to the following failed restriction(s):
2010-11-24 14:44:20 Slp: Condition "Is the user's scenario set to ComponentUpdate" did not pass as it returned true and false was expected.
2010-11-24 14:44:20 Slp: ----------------------------------------------------------------------
2010-11-24 14:44:20 Slp: Running Action: CloseUI
2010-11-24 14:44:20 Slp: Stop Action
0
Comment
Question by:Hentie_SA
  • 3
  • 2
5 Comments
 
LVL 4

Accepted Solution

by:
rlog earned 500 total points
ID: 34205732
http://msdn.microsoft.com/en-us/library/ms143393.aspx - you can upgrade to SQL 2008 Developer. And from there you can upgrade to SQL 2008 Enterprise.
0
 

Author Comment

by:Hentie_SA
ID: 34239876
Well, I struggled to get hold of a Developers edition copy and tried to update it using Evaluation mode with the same effect. Same errors.
0
 

Author Comment

by:Hentie_SA
ID: 34239878
Well, I struggled to get hold of a Developers edition copy and tried to update it using Evaluation mode with the same effect. Same errors.
0
 
LVL 4

Expert Comment

by:rlog
ID: 34240354
What errors did you get? Your alternative is to upgrade SQL 2000 dev to SQL 2000 Ent and then SQL 2008 Ent upgrade. Alternatively you can uninstall and install sql 2008 with same settings (pay attention to collation) and attach databases.
0
 

Author Closing Comment

by:Hentie_SA
ID: 34280695
I couldn't upgrade to 2008 Developer for some reason, so opted to upgrade to 2005 Developer first, then to 2008. That worked fine.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question