When you try to upgrade Microsoft Windows SharePoint Services 2.0 to Microsoft Windows SharePoint Services 3.0, you receive the following error message:
Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit. The most likely reasons for Prescan to skip a list are covered in the Knowledge Base article at: http://go.microsoft.com/fwlink/?linkid=69958&clcid=0x409. For more information about which lists were not upgraded, see the upgrade log file at LocationOfLogFile.
This issue occurs if one of the following conditions is true:
- The content database contains one or more orphaned lists. For example, a list may not have a parent Windows SharePoint Services 2.0 site.
- The content database contains one or more Windows SharePoint Services 2.0 sites that use an included path. Additionally, the included path is not defined on the server.
To resolve this issue, use one of the following methods, as appropriate for your situation.
Method 1: Remove orphaned lists from the content database
To remove orphaned lists from the content database, install the hotfix that is documented in article 918744 in the Microsoft Knowledge Base.
Article 918744 is the same article that is referenced in the URL in the error message that is mentioned in the "Symptoms" section. The hotfix introduces a new databaserepair
command-line operation that you can use together with the Stsadm.exe command-line tool to repair content databases in Windows SharePoint Services 2.0.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services
After you apply the hotfix, use the Stsadm.exe command-line tool together with the databaserepair
command-line operation to detect and delete orphaned items in the content databases. To do this, follow the steps in article 918744.Important
command-line operation removes orphaned items from content databases in Windows SharePoint Services 2.0. If orphaned items are present in the configuration database, you must clean up the orphaned items in the configuration database. To do this, use the Window SharePoint Services Central Administration tool to remove the content databases from the virtual server. Then, reattach the content databases to the virtual server. For information about how to clean up orphaned items in the configuration database, see "Step 3: Remove and then reattach the content databases on the virtual server" in article 918744.
After you perform the steps in article 918744, run the Windows SharePoint Services 3.0 Setup program to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0.
Method 2: Add an included path
- Review the Upgrade.log file to determine the included path that is missing.
- Add an included path. To do this, follow these steps:
- Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
- On the Central Administration page, click Configure virtual server settings under Virtual Server Configuration.
- On the Virtual Server List page, click the virtual server that you want to configure.
- On the Virtual Server Settings page, click Define managed paths under Virtual Server Management.
- In the Add a New Path area, type the path in the Path box.
- Click Included path, and then specify the path type that you want in the Type box.
- Click OK.
After you add an included path, run the Prescan.exe tool. Verify that the tool finishes successfully. Then, run the Windows SharePoint Services 3.0 Setup program to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0.
For more information about the Stsadm.exe command-line tool, see the "Command-Line Operations" topic, the "Command-Line Parameters" topic, and the Command-Line-Properties" topic in the "Reference" chapter of the Microsoft Windows SharePoint Services 2.0 Administrator's Guide. To obtain the Microsoft Windows SharePoint Services 2.0 Administrator's Guide, visit the following Microsoft Web site: