Bill Baer

Senior Product Marketing Manager (SharePoint), Microsoft Certified Master for SharePoint, Microsoft Corporation

Understanding PRESCAN.EXE Errors

Understanding PRESCAN.EXE Errors

  • Comments 72
  • Likes

*UPDATED 5/22/2007 

I put together this post as a follow-up to my initial PRESCAN topic "Understanding PRESCAN.EXE in MOSS 2007"; hopefully, this will provide insight into the most common PRESCAN errors administrators may encounter and remediation steps where available. These solutions may not fit every environment due to the natural differences in topologies, hosting models, versioning, and infrastructure.

Error:

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

  1. The Content Database contains one or more orphaned Webs.  A Web may not have a parent Windows SharePoint Services 2.0 site.

Find and repair orphaned Webs, Lists, and Document Libraries using STSADM -o databaserepair -url http://<server> -databasename <WSS2.0_Content_Database> [-deletecorruption].  This operation requires hotfix KBs 918742 and/or 918744.  Joel Oleson has a great post on these hotfix KBs here.

Error:

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.

  1. A Windows SharePoint Services 2.0 language pack or Windows SharePoint Services 2.0 application template is not installed.
  2. Templates used by SharePoint Portal Server 2003 can be incorrectly identified during the pre-upgrade scan as custom templates unless you use the preupgradescanconfig.xml file when you perform the scan. This file contains additional logic to identify the portal site templates as standard templates used by SharePoint Portal Server 2003 rather than as custom templates based on Windows SharePoint Services 2.0.

Install language packs and application templates as required or use the preupgradescanconfig.xml file when you perform the scan.

Error:

[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

  1. Required fields are NULL on a List within a Web and/or Windows SharePoint Services 2.0 site.  As an example, a Discussion Board may contain one or more posts with a blank Subject and/or Body field. 

Using the reported ListId, Identify the Web and/or Windows SharePoint Services 2.0 site hosting the List and correct the input as necessary.

Error:

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.

  1. The content database contains one or more orphaned lists. For example, a list may not have a parent Windows SharePoint Services 2.0 site.
  2. 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.

See http://support.microsoft.com/kb/923904 for additional information.

Error:

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

  1. A Windows SharePoint Services 2.0 Inclusion path is missing.  Confirm all inclusion paths used by Windows SharePoint Services 2.0 sites are available.

If PRESCAN fails on any Content Database you will receive an error when attempting to run the upgrade which will render as follows:

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.

Error:

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

  1. The content database contains one or more orphaned lists. For example, a list may not have a parent Windows SharePoint Services 2.0 site.

Error:

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

  1. The configuration database contains one or more orphaned or inaccessible site collections. Confirm the site exists or unlock the site collection in Central Administration. If the site does not exist, recreate the site collection and run PRESCAN.

Error:

This server is not the indexer of this search application.

  1. This issue occurs if the Windows SharePoint Services 3.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 or to query the Windows SharePoint Services database on the computer that is running SQL Server.  To resolve this issue visit http://support.microsoft.com/kb/923896/en-us.

Error:

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.

  1. This issue occurs if psconfig.exe was run prior to successfully running the pre-upgrade scan tool in the server farm.  Run the pre-upgrade scan tool and resolve any reported issues before running psconfig.

To determine where PRESCAN failed you can run the attached query against your content databases, the results of the SQL statement are the Site Collections in which PRESCAN was unable to properly scan and/or access through the SharePoint Object Model.

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

Error:  “An outbound zone URL is configured for something other than the default zone on virtual server http://fabrikam/, and no default zone outbound URL is defined.  This is not supported, and must be corrected before upgrading.”

  1. This error occurs when no defaultzoneoutgoingurl is defined for the Windows SharePoint Services 2.0 virtual server; in Windows SharePoint Services 2.0 it was valid to not have a URL in the default zone while subsequently having URLs in non-default zones.  You can correct this issue by using the stsadm.exe -o addzoneurl operation or alternatively accessing the values through the Object Model (code sample below).

You can review the properties programmatically in the SPVirtualServer.Config object; a example of these values of the properties is attached below.

Example:

DefaultZoneOutgoingUrl = ""
IntranetZoneOutgoingUrl = ""
InternetZoneOutgoingUrl = ""
ExtranetZoneOutgoingUrl = "http://fabrikam/"

The outgoing URLs are stored in the configuration database in the "Properties" field of "VirtualServers" table.  See an example of the "Properties" field value below:

<?xml version="1.0" encoding="utf-16"?><properties><version value="1" /><filter><inclusions><inclusion>/</inclusion><inclusion>/sites/*</inclusion><inclusion>/personal/*</inclusion></inclusions><exclusions><exclusion>/uddi</exclusion><exclusion>/uddipublic</exclusion><exclusion>/mapaweb</exclusion></exclusions></filter><miscellaneous><property name="securityvalidation-expire" value="True" /><property name="virtualserverpermsmask" value="-1" /><property name="data-retrieval-services-oledb-providers" value="DB2OLEDB;IBMDADB2;MSDAORA;OraOLEDB.Oracle;SQLOLEDB" /><property name="extranetzoneoutgoingurl " value="http://someurl/" /><property name="ssc-contact" value="no" /><property name="send-ad-email" value="True" /><property name="ssc" value="yes" /><property name="securityvalidation-enabled" value="True" /><property name="securityvalidation-timeout" value="30" /></miscellaneous></properties>

To access the values through the Object Model in the event te STSADM operation does not resolve the issue, use the sample code below as guidance.

SPGlobalAdmin ga = new SPGlobalAdmin();
SPVirtualServer vs = ga.OpenVirtualServer(new Uri(“http://” + System.Environment.MachineName));
vs.Config.ExtranetZoneOutgoingUrl = null;
vs.Config.Properties.Update();

You can then remove the <property name="extranetzoneoutgoingurl " value="http://fabrikam/" /> property which should resolve the issue.

Comments
  • PingBack from http://mikewalsh.bilsimser.com/PermaLink,guid,2c91179a-250f-488a-998c-a23b16f11b10.aspx

  • I've made several updates and revisions to my previous post " Understanding PRESCAN.EXE Errors ", I hope

  • MSDN Windows SharePoint Services Run the pre-upgrade scan tool (Windows SharePoint Services) http://technet2.microsoft.com/Office/en-us/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx?mfr=true

  • This is great William !

    But you dont have any "What do I do if I get this error" information on this blog...

    Its nice to know I have "orphaned lists" .. but what do I do about it ?????   I have tried to run the stsadm -o databaserepair  but it gives me some other error (of which there is no documentation) about needing to run it from some server farm machine with permission to SQL

    Then it says to run the configuration wizard to fix the issue.. but I cant run the configuratioin wizard because it says I need to run prescan without errors..

    Nice catch 22.

    This is PAINFUL !

  • If you have applied hotfix KB 918744 http://support.microsoft.com/kb/918744/, you can use the -databaserepair parameter with the -deletecorruption switch to resolve orphaned list issues, if you are receiving errors indicating that permission to the SQL  database server is required, you should confirm the account under which you are running STSADM operation has sysadmin privilege on the SQL database server or logon to the front-end web server using the system service account under which SharePoint Products and Technologies is running.  Also STSADM does not run across server farms, you should also confirm the front-end web server running the command is a member of the farm hosted on the SQL database server.

    Hope this helps!

  • William,

    I had 5 orphan sites, than I run the stsadm with the -databaserepair and -deletecorruption parameters.

    Then I run stsadm only with -databaserepair parameter and it show, that i don't have orphan objects:

    <OrphanedObjects Count="0" />

    All works fine, but when I run prescan tool again, i still got these errors for almost all my lists:

    "Error: The following list has not been scrubbed: Id=xxx, Name=ListName, Containing Web=sites/siteCollection/SiteName"

    Can you help me

  • This would indicate that you have a List that does not have a parent Windows SharePoint Services 2.0 site.  Using the attached SQL query you can determine what Site Collections have not been scrubbed by PRESCAN.  If no results are returned all Site Collections have been successfully scrubbed.  I would recommend you run another -databaserepair operation against the affected database to ensure the reporting results are accurate and you are not receiving any 'cached' results.  You may also track the list back to its parent Site through joining the ListId and Id from the Webs table to identify where the problem resides.

    SELECT FullUrl, Id

    FROM Sites

    WHERE bitflags NOT LIKE '262144'

  • I am having the same issue as reported above.  prescan tool reports I have many orphaned lists.  running a databaserepair reports I have no orphaned objects.

    any ideas?

  • I am having the same issue as reported above.  prescan tool reports I have many orphaned lists.  running a databaserepair reports I have no orphaned objects.

    any ideas?

  • Using the List Id reported by PRESCAN you will be able to determine the parent Site Collection/Web using the attached SQL query.  Typically an unusually high number of orphaned Lists can be attributed to a unique orphaned Site Collection/Web.  By removing the offending Site Collection/Web you can remediate this type of problem; otherwise, you can address the problem from the List level reported by the attached SQL query.

    SELECT Lists.tp_Title, Lists.tp_Description, Webs.FullUrl FROM Lists

    INNER JOIN Webs

    ON Webs.Id=Lists.tp_WebId

    WHERE Lists.tp_ID = '<List_Id_Reported_in_PRESCAN>'

  • Do you know if prescan.exe can be run on a specific port?

    e.g. prescan.exe /v http://myserver:1959?

    Thanks,

    Michael.

  • Michael;

    PRESCAN is capable of running against a specific port.  If PRESCAN reports the virtual server cannot be accessed, you should check and confirm the following configurations and run the pre-upgrade report tool (PRESCAN.EXE) again:

    1. Host header value, TCP, and SSL port settings in Internet Information Services for the Virtual Server
    2. Value for Virtual Server in the front-end web server HOSTS table (C:\WINDOWS\System32\drivers\ETC\HOSTS)
    3. Alternate portal site URLs
    4. WSS SP2 installed
    5. Virtual server has been upgraded after WSS SP2 installation

    Using the port settings sample you provide I was able to successfully obtain PRESCAN results in my lab.

    02/03/2007 11:37:57 Scanning SPWeb: http://spsites:1959/Topics

    02/03/2007 11:37:57   Web is using custom template "SPSTOC".

    02/03/2007 11:37:57   Updating list schema in web.

    02/03/2007 11:37:57 Checking if Server="X-REDMMSSPTRS01";Database="SPSites1_SITE";Trusted_Connection=yes;App="prescan.exe" is a WSS V2 SP2 database.

    02/03/2007 11:37:57 Checking if any site has not yet been scanned in Server="X-REDMMSSPTRS01";Database="SPSites1_SITE";Trusted_Connection=yes;App="prescan.exe".

    02/03/2007 11:37:57 Checking if any list has not yet been scrubbed in Server="X-REDMMSSPTRS01";Database="SPSites1_SITE";Trusted_Connection=yes;App="prescan.exe".

    02/03/2007 11:37:57 Scan finished without failure.

    02/03/2007 11:37:57 ===============================Logs===============================

    02/03/2007 11:37:57 Log file: C:\DOCUME~1\MS7C45~1\LOCALS~1\Temp\PreupgradeReport_633060994741085700_Log.txt

    02/03/2007 11:37:57 Summary file: C:\DOCUME~1\MS7C45~1\LOCALS~1\Temp\PreupgradeReport_633060994741085700_Summary.xml

    02/03/2007 11:37:57 ==============================Totals==============================

    02/03/2007 11:37:57 Number of sites skipped (already scanned):   0

    02/03/2007 11:37:57 Number of sites scanned:   1

    02/03/2007 11:37:57 Number of broken sites:   0

    02/03/2007 11:37:57 Number of webs scanned:   18

    02/03/2007 11:37:57 Number of broken webs:   0

    02/03/2007 11:37:57 Number of webs using custom template:   18 (100% of total).

    02/03/2007 11:37:57 Number of pages scanned:   298

    02/03/2007 11:37:57 Number of unghosted pages:   0

  • Here is a great post on what prescan.exe errors really mean when encountered during their run prior to

  • I've updated my post Understanding PRESCAN.EXE Errors to include two new errors and solutions. Read more

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment