Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. How to troubleshoot a failed upgrade to SQL Server 2008

How to troubleshoot a failed upgrade to SQL Server 2008

Symptoms

When you try to upgrade Microsoft SQL Server 2000 or Microsoft SQL Server 2005 to Microsoft SQL Server 2008, the upgrade operation fails. Additionally, you may receive the following error message:
The access control list is not in canonical form
If you try to upgrade again, all the options on the Select Features page are unavailable. Additionally, you receive the following error message in the status bar:
There are no features selected for upgrade

↑ Back to the top

Cause

This problem occurs when a previous attempt to upgrade the instance of SQL Server 2000 failed and you try to upgrade again.

↑ Back to the top

Resolution

To resolve this problem, you must examine the summary log file and perform the actions that are specified under the Final Result entry. To do this, follow these steps:
  1. Locate the summary log file of the failed upgrade. Typically, the summary log file is located in the following folder:
    %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\LOG\
    The name of the summary log file resembles the following name:

    Summary_Server_Name-Node1_Date_Time.txt
  2. Open the summary log file, and then locate the Final Result entry. This entry specifies the actions that you must take to complete the upgrade. For example, you may see an entry that resembles the following entry:
    SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server using the following command line, and then rerun SQL Server Setup. Uninstall command line:
    setup /q /action=uninstall /instanceid=CLUSTER1 /features=SQLEngine,Replication,FullText
  3. Investigate and resolve the problem that caused the failure. Then, continue with the remaining steps.
  4. At the command prompt, move to the following folder:

    %Program Files%\Microsoft SQL Server\100\Setup Bootstrap
  5. At the command prompt, type the command that you identified in the Final Result entry in step 2, and then press ENTER. For example, if the Final Result entry resembles the example entry in step 2, type the following command, and then press ENTER:
    setup /q /action=uninstall /instanceid=CLUSTER1 /features=SQLEngine,Replication,FullText
  6. After the unistallation is complete, restart the upgrade to SQL Server 2008.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the log files in SQL Server 2008, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/ms143702(SQL.100).aspx
For more information about SQL Server 2008, visit the following Microsoft Web site:
http://www.microsoft.com/sqlserver/2008/en/us/default.aspx

↑ Back to the top

Keywords: kb, kbprb, kbentirenet, kberrmsg, kbtshoot, sql2008relnoteconfiguration, misc_migrate_32718, sql2008relnoteinstallation, sql2008relnoteupgrade, sql2008relnotereadfirst, sql2008relnote

↑ Back to the top

Article Info
Article ID : 955399
Revision : 2
Created on : 4/13/2018
Published on : 4/13/2018
Exists online : False
Views : 95