Microsoft KB Archive/937291

Knowledge Base

You receive an error message when you run the pre-upgrade scan tool (Prescan.exe) to scan Windows SharePoint Services 2.0 sites before you upgrade to Windows SharePoint Services 3.0

Article ID: 937291

Article Last Modified on 10/31/2007

---

APPLIES TO

• Microsoft Windows SharePoint Services 3.0

---

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you run the pre-upgrade scan tool (Prescan.exe) to scan Microsoft Windows SharePoint Services 2.0 sites before you upgrade to Microsoft Windows SharePoint Services 3.0, you receive one of the following error messages:

• Error message 1

  There is no Web named /<path>/<site>

• Error message 2

  Cannot locate list definition required for upgrade. Check to ensure you have all templates and language packs installed. Error: Exception scanning web: http://<server>/<path>/<site>
  System.IO.FileNotFoundException: The system cannot find the file specified.

• Error message 3

  [UpgradeDiscussionLists] [3.0.87.0] [ERROR] [12/11/2006 5:06:15 PM]: Data is Null. This method or property cannot be called on Null values.
  
  [UpgradeDiscussionLists] [3.0.87.0] [ERROR] [12/11/2006 5:06:15 PM]: Item update failed for list 3cc63b2b-8a42-4ef3-bfa4-6e40f4827ec6, thread 20051208-1643-2400-a3fe-67a3e9495a11, ordering 20051208164324

• Error message 4

  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 the lists that are not upgraded, see the upgrade log file.

• Error message 5

  PRESCAN failed for site /<prefix>/<site>. The site could not be access through the SharePoint Object Model.

• Error message 6

  FAILED to persist field schema of lists in web [insert URL of site]
  Error: The following site has not been scanned. Id = df843563-2961-41ff-ad61-0414c67d7305 and Url = abc/TestABC
  Error: The following list has not been scrubbed: Id=6bfb5f3d-fa4b-4c71-b251-0778e0e1018a, Name=Web Part Gallery, Containing Web=abc/TestABC

• Error message 7

  The site http://<server>/<path>/<site> cannot be opened. The site might be corrupted. To fix this problem, delete the site and recreate it.

  Error: The following site has not been scanned. Id = f85aaeee-b93e-491f-b2ff-88d449f1166f and Url = <path>/<site> http://support.microsoft.com/kb/918744

• Error message 8

  This server is not the indexer of this search application.

• Error message 9

  An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.
  Additional exception information: The pre-upgrade scan tool has not yet been run on all servers in the farm. You must run the pre-upgrade scan tool before you can continue with the upgrade process. Run the tool from the following path: c:\program files\common files\Microsoft shared\web server extensions\12\bin\prescan.exe. After you have reviewed any issues found by the tool, you can run psconfig.exe again to continue the upgrade process.

• Error message 10

  Skipping virtual server: . Server state = NeedUpgrade. Most likely this virtual server is not extended with WSS v2.
  
  Microsoft.SharePoint.SPException: Unable to get global configuration data. --->
  System.Runtime.InteropServices.COMException (0x81070550): Unable to get global configuration data.
  at
  Microsoft.SharePoint.Library.SPRequestInternalClass.GetVirtualServerProperty(Int32 lIISInstanceID, Boolean bInXMLFormat, String bstrName, String& pbstrValue, Int64& plVersion)

CAUSE

Cause of error message 1

This issue occurs if the content database contains one or more orphaned Web sites. An orphaned Web site is a Web site that does not belong to a Windows SharePoint Services 2.0 parent Web site.

Cause of error message 2

This issue occurs if a Windows SharePoint Services 2.0 language pack or a Windows SharePoint Services 2.0 application template is installed incorrectly. Some Microsoft Office SharePoint Portal Server 2003 templates may be incorrectly identified as custom templates during the pre-upgrade scan process.

Cause of error message 3

This issue occurs if some required fields are set to NULL on a list that resides on a Windows SharePoint Services 2.0 site. For example, a discussion board may contain one or more posts that have a blank Subject field or a blank Body field.

Cause of error message 4

This issue occurs if the content database contains one or more orphaned lists. An orphaned list is a list that does not belong to a Windows SharePoint Services 2.0 parent site. This issue may also occur if the content database contains one or more Windows SharePoint Services 2.0 sites that use an included path. However, the included path is not defined on the server.

Cause of error message 5

This issue occurs if Prescan.exe detects that a Windows SharePoint Services 2.0 inclusion path is missing.

Cause of error message 6

This issue occurs if the content database contains one or more orphaned lists. An orphaned list is a list that does not belong to a Windows SharePoint Services 2.0 parent site.

Cause of error message 7

This issue occurs if one of the following conditions is true:

1. The Windows SharePoint Services 2.0 configuration database contains one or more orphaned sites or one or more inaccessible site collections.
2. The content database contains one or more orphaned lists. An orphaned list is a list that does not belong to a Windows SharePoint Services 2.0 parent site.

Cause of error message 8

This issue occurs if the Windows SharePoint Services 2.0 database is hosted on a separate computer that is running Microsoft SQL Server. In this situation, the Windows SharePoint Services search logon account may not have the correct permission to access the Windows SharePoint Services database or to query the Windows SharePoint Services database on the computer that is running SQL Server.

Cause of error message 9

This issue occurs if one or more of the following conditions are true:

1. You ran Psconfig.exe in the server farm before you ran Prescan.exe.
2. You did not successfully run the "SharePoint Products and Technologies Configuration Wizard" in Windows SharePoint Services 3.0 before you installed Microsoft Office SharePoint Server 2007. In this situation, the SharePoint Portal Server 2003 configuration wizard cannot be upgraded.

Cause of error message 10

This issue occurs if the Windows SharePoint Services 2.0 configuration database is corrupted.

RESOLUTION

Resolution for error message 1

To resolve this issue, follow these steps:

1. Install the software updates that are described in the following articles in the Microsoft Knowledge Base:

   918742 Description of a new command-line operation that is available for the Spsadm.exe command line tool that you can use to clean up orphaned items in the configuration database in SharePoint Portal Server 2003

   918744 Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services

2. Repair any orphaned Web sites, lists, and document libraries. To do this, run the following command at the command line:

   Stsadm -o databaserepair -url http://<ServerName> -databasename <WSS2.0_Content_Database> -deletecorruption

   Note In this command, <ServerName> is the name of the Windows SharePoint Services 2.0 server. Additionally, <WSS2.0_Content_Database> is the name of the Windows SharePoint Services 2.0 content database.

Resolution for error message 2

To resolve this issue, reinstall the language packs and the application templates, as appropriate for your situation. Additionally, you can use the Preupgradescanconfig.xml file when you perform the scan. For example, run the following command at the command line:

prescan.exe /c preupgradescanconfig.xml /all

The Preupgradescanconfig.xml file contains additional logic to help find the portal site templates that are used by SharePoint Portal Server 2003 as standard templates instead of as custom templates that are based on Windows SharePoint Services 2.0.

Resolution for error message 3

To resolve this issue, use the ListId value in the error message to determine the Web site or the Windows SharePoint Services 2.0 site that hosts the list. Then, add information in the required fields that are set to NULL.

Resolution for error message 4

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

923904 Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit

Resolution for error message 5

To resolve this issue, make sure that all inclusion paths that are used by Windows SharePoint Services 2.0 sites are available.

Resolution for error message 6

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

923904 Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit"

Resolution for error message 7

To resolve this issue, use one of the following methods:

• Confirm that the Windows SharePoint Services 2.0 site exists. Or, unlock the site collection in SharePoint Central Administration. If the site does not exist, re-create the site collection. Then, rerun Prescan.exe.
• Use Smigrate.exe to back up the Windows SharePoint Services 2.0 site and then to restore the Windows SharePoint Services 2.0 site. This can help resolve issues that are caused by orphaned lists.
  

Note Smigrate.exe removes any custom permissions in the Windows SharePoint Services 2.0 site.

Resolution for error message 8

For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

923896 Error message when you try to run the Windows SharePoint Services 3.0 pre-upgrade scan tool from the command line: "This server is not the indexer of this search application"

Resolution for error message 9

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, use one of the following methods:

• Rerun Prescan.exe, and then resolve any reported issues before you run Psconfig.exe.
• Remove SharePoint Server 2007 by using the "Add or Remove Programs" item in Control panel, and then upgrade SharePoint Portal Server 2003 to SharePoint Server 2007. To do this, follow these steps:
  1. Click Start, click Run, type cmd in the Open box, and then click OK.
  2. Locate the following registry subkey:

     HKEY_LOCAL_MACHINE\software\Microsoft\shared tools\web server extensions\12.0\wss

  3. Change the SetupType value to CLEAN_INSTALL.
  4. In Control Panel, double-click Add or Remove Programs, and then click Remove under Microsoft Office SharePoint Server 2007.
  5. In Registry Editor, locate the following registry subkey:

     HKEY_LOCAL_MACHINE\software\Microsoft\shared tools\web server extensions\12.0\wss

  6. Change the SetupType value to V2V_INPLACE_UPGRADE.
  7. Run the configuration wizard, and then upgrade to SharePoint Server 2007.

Resolution for error message 10

To resolve this issue, follow these steps:

1. Click Start, point to Administrative Tools, and then click SharePoint Central Administration.
2. On the SharePoint Central Administration Web page, create a new configuration database.
3. For each virtual server that was extended, click Configure Virtual Server Settings, and then click Remove Windows SharePoint Services from Virtual Server. Remember to keep the existing content databases.
4. Use a blank content database to reextend the virtual server.
5. Under Manage Content Databases, remove the blank content database, and then add the existing content database.

If Prescan.exe cannot upgrade a content database, you may receive the following error message when you try to upgrade to Windows SharePoint Services 3.0:

The pre-upgrade scan tool has not yet been run on this database SPContentDatabase Name=Some_Content_Database Parent=SPDatabaseServiceInstance. You must run the pre-upgrade scan tool before you can continue with the upgrade process.
Run the tool from the following path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\prescan.exe.

Error: Prescan has encountered sites or lists that were not updated because they cannot be accessed using the SharePoint Products and Technologies object model. 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.

To determine how the Prescan.exe error occurs, you can run an SQL query against the content databases. To do this, follow these steps:

1. Click Start, point to All Programs, click Microsoft SQL Server, and then click Query Analyzer.
2. In SQL Query Analyzer, click the content database that you want to verify in the list of databases.

3. Copy the following SQL statement, paste the SQL statement in SQL Query Analyzer, and then click Execute.

   SELECT FullUrl, Id
   
   
   FROM Sites
   
   
   WHERE bitflags NOT LIKE '262144'

   This query returns the site collection names that Prescan.exe could not successfully scan or access.

Additional query words: WSS2.0 WSS3.0

Keywords: kbinfo kbtshoot kbprb kbexpertiseinter KB937291

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.