Understanding PRESCAN.EXE Errors


*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 LIKE262144


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 (69)

  1. Anonymous says:

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

  2. Anonymous says:

    Joel Oleson’s Blog – SharePoint Land : Don’t be afraid of Prescan – Part 1: http://blogs.msdn.com/joelo/archive/2007/04/13/don-t-be-afraid-of-prescan-part-1.aspx

  3. Anonymous says:

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

  4. Anonymous says:

    L’un sans l’autre, ce serait comme Minus sans Cortex (pour les plus jeunes) ou Laurel sans Hardi. Plus

  5. Anonymous says:

    Upgrading Team Foundation Server 2005 to 2008 SP1

  6. Anonymous says:

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

  7. Anonymous says:

    William has an awesome blog entry that tells you some of the details of how you can tell what some…

  8. Jason,

    The error "Cannot locate the list definition required for upgrade." indicates a Windows SharePoint Services 2.0 language pack or Windows SharePoint Services 2.0 application template is not installed. ‘

    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 ensuring you have identified and defined any custom templates.

  9. 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’

  10. 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:WINDOWSSystem32driversETCHOSTS)
    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~1MS7C45~1LOCALS~1TempPreupgradeReport_633060994741085700_Log.txt

    02/03/2007 11:37:57 Summary file: C:DOCUME~1MS7C45~1LOCALS~1TempPreupgradeReport_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

  11. Mitja;

    It is very likely what you have is either a site collection residing in more than one content database and/or configuration database orphan.  Typically the knowledge base articles I reference in this post will address those orphans and at other times CSS support is required.  See my Other Resources section for contact information.  With that said, I would first determine whether or not the site collection renders, if it renders the problem is likely a twin; otherwise, if it is not referenced in the configuration database, then it’s a standard content database orphan.  You may want to start by attempting to delete the site collection using the STSADM -o deletesite operation, detaching and then reattaching the content database, and/or optionally attempting remediation through the KB hotfixes referenced above.  Cory Burns also has some good information on orphans and remediation as an additional resource at http://blogs.technet.com/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx.

  12. Anonymous says:

    Between Shane’s prescan post (view comments for more details) , Bill’s prescan wisdom and a few of my

  13. Anonymous says:

    I wanted to point you to some recent content on upgrade and introduce you to some partners that otherwise

  14. Anonymous says:

    After setting up 10 SPS03 portals for Upgrade testing, I began the MOSS07 install. Install .Net Framework

  15. pascal says:

    Thanks William,

    I opened a ticket in MS support to get the patch !

    Pascal

  16. Anonymous says:

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

  17. The error System.IO.FileNotFoundException: The Web site that is referenced here is not in the configuration database indicates there are possibly orphaned objects in your server farm.  KB hotfixes

    http://support.microsoft.com/default.aspx?scid=KB;%5bLN%5d;918742 and
    http://support.microsoft.com/kb/918744 will help you identify and remove those objects.  Cannot get content database Id indicates that the content databases ID cannot be retrieved from the configuration database.   There are a number of possible causes
    for this and can include issues as the result of connectivity.  I would following the recommendations above to remove orphaned objects and additionally ensure you can render the portal (http://golf) from
    the web front-end server prior to running PRESCAN.  If the portal does not render from the web front-end, check the host header entries in IIS for golf and make sure it exists in addition to a mapping in the servers hosts table.

  18. Anonymous says:

    Prescan is your friend. Without prescan you *WILL* fail your upgrade from WSS 2.0 or SPS 2003 upgrade

  19. PRESCAN will check for the existence of a root site collecton; if a root site collection does not exist it will be referenced in the pre-upgrade scan report.  You can either create a root site collection and/or upgrade without the root site collection present; however, I recommend testing the upgrade prior to ensure no post-upgrade issues will result in your production environment.

  20. Michael;

    In your scenario, the List Id is 85dee5b4-1dd5-449b-b5d3-c57447477854.  Generally a NULL value error is indicative of a problem determined to be within this specific list, commonly, a missing required field, for example, a missing Subject and/or Body field in a Discussion Board, etc.  To locate the offending list, you can use the following T-SQL statement run against the content database where the error is reported:

    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>’

  21. The initial error indicates that the content database could not be identified – as a result PRESCAN will be unable to scrub the sites hosted in that content database.  I’d first confirm the sites render, the host header mappings in IIS are correct and relavent to the server farm, detach and attach the database to refresh the content database ID in the configuration database and run PRESCAN.

  22. Len;

    Using the template id referenced in the PRESCAN error, I would recommend running PRESCAN using the PREUPGRADESCANCONFIG.xml file introducing that template id.  The example below is a typical PREUPGRADESCANCONFIG.xml file, in your situation I would add a line <customTemplate id="95"/> and rerun the scan; otherwise, ensure all language packs and templates are installed in the environment where the databases is being scanned.

    <?xml version="1.0" encoding="utf-8"?>

    <configurations>

     <customTemplate id="15"/>

     <customTemplate id="20"/>

     <customTemplate id="21"/>

     <customTemplate id="22"/>

     <customTemplate id="30"/>

     <customTemplate id="31"/>

     <customTemplate id="32"/>

     <customTemplate id="33"/>

     <customTemplate id="34"/>

     <customTemplate id="35"/>

     <customTemplate id="36"/>

    </configurations>

  23. Anonymous says:

    I encountered a problem recently whilst trying to do a Database Migration for MySites. Running PRESCAN

  24. Pascal –

    The Webs sites returned as a result of the query would indicate 17 site collections/sites that we’re not scrubbed by PRESCAN.  I would recommed using the new command line operation -databaserepair (requires KB918742/KB918744).  This operation will identify any orphaned objects to include site collections/webs, lists, and document libraries.  Using the -deletecorruption parameter you can clean those objects and re-run PRESCAN.  In addition to applying the referenced query to determine whether or not all of the Web sites were touched by PRESCAN.

  25. Veeraj,

    I would recommend running PRESCAN using http:<VirtualServerUrl> if you are encountering the error using the /ALL argument additionally 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.  You should also verify that if using IIS hostheaders and/or alternate access mappings (alternate urls) that you are running PRESCAN using the virtual server argument.

  26. 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>’

  27. Dave;

    The preupgrade scan configuration file could not be located or read at/from the specified path.  Copy PREUPGRADESCANCONFIG.XML to the directory where PRESCAN.EXE resides and run PRESCAN.EXE <arg> PREUPGRADESCANCONFIG.XML.

  28. Mandarin;

    The following information should assist in resolving the error you referenced:

    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/&quot;

    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/&quot; /><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/&quot; /> property which should resolve the issue.

  29. 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!

  30. Rahul;

    I would first check to ensure the site collection /sites/ps renders in addition to verifying its current quota and lock status to confirm the site collection is not nearing or has exceeded its quota in addition to being accessible and not read/write locked.  You can use Central Administration to confirm these items.  The site collection may also be in an orphaned state and inaccessible to the -databaserepair operation in which case you can attempt deleting the site collection using the SharePoint administration tool (STSADM) and/or detaching and reattaching the database to the SharePoint Products and Technologies server farm.

  31. Generally you will want to ensure that 2.0 templates have a corresponding 3.0 template; otherwise, if the error persists, consider using the PREUPGRADESCANCONFIG.XML configuration file with PRESCAN.

  32. To obtain the hotfix packages, you will need contact Microsoft Product Support Services to obtain the hotfix.

    For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

    http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support).

  33. Niyaz;

    The error is indicative of an orphan site within your content database; to resolve the orphaned site collection consider using KB918744/918742 at http://support.microsoft.com/kb/918744.

  34. Anonymous says:

    Body: Just finished my first session at TechEd New Zealand &quot;OFC 304 Microsoft Windows SharePoint

  35. Anonymous says:

    Body: A few people have asked me how to approach migrations and upgrades for previous versions of SharePoint

  36. Paul;

    The exception appears to be generated when attempting to access the specific URL, I would check to ensure the proper syntax and arguments are being passed to PRESCAN in addition to ensuring the site collection can be rendered and is not in a locked (read/write) state or is beyond its quota.

  37. System.FormatException: Input string was not in a correct format. indicates a variable was not properly passed to PRESCAN.EXE.  Check the syntax of the command, if using PRESCAN /ALL, try using PRESCAN <http://VirtualServerUrl&gt;.

  38. Anonymous says:

    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

  39. Steve says:

    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 !

  40. Barbara says:

    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

  41. Eric Berry says:

    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?

  42. Eric Berry says:

    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?

  43. Michael Herman (Parallelspace) says:

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

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

    Thanks,

    Michael.

  44. mike says:

    William, I’m pulling my hair out and hoping you can help me.  We are trying to upgrade to WSS3 from WSS2.  We run the prescan tool and come up with:

    04/09/2007 12:42:21 Error: Cannot get content database Id.

    04/09/2007 12:42:21 System.IO.FileNotFoundException: The Web site that is referenced here is not in the configuration database.

      at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange)

      at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)

      at Microsoft.SharePoint.SPSite.c()

      at Microsoft.SharePoint.SPSite.get_ID()

      at Microsoft.SharePoint.PreupgradeReport.Scan.GetContentDBBySite(SPSite site, SPVirtualServer vs)

    04/09/2007 12:42:21 Querying SPSite quota and locks on ba9ddaf3-c5f6-44e6-a414-2ddf31fdc617

    04/09/2007 12:42:21 Turning off quota and locks on SPSite ba9ddaf3-c5f6-44e6-a414-2ddf31fdc617

    04/09/2007 12:42:21 Scanning SPWeb: http://golf/central/Administration

    04/09/2007 12:42:21   Updating list schema in web.

    And of course goes on and on.  I ran the databaserepair tool but did not find any orphaned objects.  We have a very easy deployment of this on a single server with about 25 sites.  The only customization that was done was bringing a few pages into Frontpage 2003 to add a link on the Quicklaunch bar.  Other than that, there is nothing fancy about installation.  Any thoughts?

    Thanks,

    Mike

  45. mike says:

    Thank you so much for your reply…what do mean exactly when you say "first confirm the sites render, the host header mappings in IIS are correct and relavent to the server farm"  How would one go about checking that?  Again, thanks your reply!

    Mike

  46. mike says:

    Our Sharepoint virtual server that contains our content database is the "Default Web Site" in IIS.  Within the wwwroot folder for that site contains an HTML index page which we created to link to separate Sharepoint sites.  I can definitely get to that page as well as the Sharepoint sites from the actual server.  

    Just so I’m clear on the hotfixes.  The stsadm.exe tool is run from the 60BIN folder correct?  Not the 12BIN that is added after 3.0 is installed?  We have 8 "Defined Managed Paths" and multiple sites under those for a total of 35 sites.  When running the database repair, do I have run 35 instances of this command for each site we have?  In running the databaserepair command on a couple of sites it has come up with "0" orphaned objects.  

    And to no avail, I did remove and reattach the content database from the "Default Web Site" virtual server.

    Thank you so much for you help!

    Mike

  47. mike says:

    I’m starting to think my problem lies within the root http://golf/ folder.  As there are no "root" sites it seems to be looking in there and not seeing anything therefore giving the error.  Any thoughts?

  48. pascal says:

    Hi William,

    I have a strange problem with my prescan !

    When I do this command:

    – "prescan /all" : I have no error, but the prescan didn’t recognize my portal, the result (in the log) is:

    05/02/2007 11:07:06 Skipping virtual server: http://myportal/. Server state = NeedUpgrade. Most likely this virtual server is not extended with WSS v2.

    – if I use this one: "prescan http://myportal&quot;, there is no error, my portal is scanned. But when I do a "addcontentdb" from MOSS2007, there is an error "You must run prescan" !

    – I used your query:

    "SELECT fullurl, bwused,certificationdate

    FROM Sites

    WHERE bitflags NOT LIKE ‘262144’ " and I found 17 web sites ! Are they orphans ? Do I need to do a repair ?

    Thanks,

    Pascal

  49. Robert says:

    Can anyone assist on this one?

    05/03/2007 08:06:07 Error: Exception while looping through virtual servers.

    05/03/2007 08:06:07 System.FormatException: Input string was not in a correct format.

      at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

      at System.Version..ctor(String version)

      at Microsoft.SharePoint.PreupgradeReport.Scan.SearchForUnscrubbedLists(SPVirtualServer curVS)

      at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneVirtualServer(SPVirtualServer curVS)

      at Microsoft.SharePoint.PreupgradeReport.Scan.Run(StringCollection argsList)

    05/03/2007 08:06:07 Scan finished with failure.

    05/03/2007 08:06:07 ===============================Logs===============================

    05/03/2007 08:06:07 Log file: C:DOCUME~1robertpLOCALS~1Temp2PreupgradeReport_633137760854491560_Log.txt

    05/03/2007 08:06:07 Summary file: C:DOCUME~1robertpLOCALS~1Temp2PreupgradeReport_633137760854491560_Summary.xml

    05/03/2007 08:06:07 ==============================Totals==============================

    05/03/2007 08:06:07 Number of sites skipped (already scanned):   0

    05/03/2007 08:06:07 Number of sites scanned:   567

    05/03/2007 08:06:07 Number of broken sites:   0

    05/03/2007 08:06:07 Number of webs scanned:   1095

    05/03/2007 08:06:07 Number of broken webs:   0

    05/03/2007 08:06:07 Number of webs using custom template:   851 (77.72% of total).

    05/03/2007 08:06:07 Number of pages scanned:   38023

    05/03/2007 08:06:07 Number of unghosted pages:   21 (0.06% of total).

  50. Chris says:

    Hi.

    I have the same problem with the prescan.exe error "Cannot get content database id".

    You’ve recommended to use the post sp2 hotfix package.:

    http://support.microsoft.com/default.aspx?scid=KB;%5bLN%5d;918742 and
    http://support.microsoft.com/kb/918744

    Where can I download this package? I only find the KB article but nowhere the hotfix for download?

    Thanks.

    Chris.

  51. Veeraj says:

    Hi William,

    I have this issue with prescan. It fails and shows the error

    "The following site has not been scanned. Id = e80b5068-6f05-48e1-98e4-a76bfe853351 and Url = /  "

    This url is nothing but portal URL, Any idea how can i proceed if prescan is unable to scan portal itself?

    Thanks in advance!

    -Veeraj

  52. Jason says:

    Hi William,

    Have you run into this error message before:

    05/24/2007 13:06:29 Cannot locate the list definition required for upgrade.  Check to ensure you have all templates and language packs installed.

    05/24/2007 13:06:29 Error: Exception scanning web: http://spsstg.edc.ca/myWorkspaces/BALearningCommunity

    05/24/2007 13:06:29 System.Runtime.InteropServices.COMException (0x80004005): Cannot complete this action.

    Please try again.

      at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(String bstrUrl)

      at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPWeb(SqlConnection connection, String vsUrl, SPVirtualServer vs, SPSite site, SPWeb web)

  53. len says:

    I get …

    Web is using a custom template ( id = 95 ) which can not be located on the web front end

    … Ideas?

    BTW, I’ve copied the databases to a new server and installed a fresh SPS 2k3 on it for the prescanning.

  54. rahul says:

    Hi,

    This is the one of the wonderful blog about prescan errors.

    Thanks baer for creating it..

    We are doing Gradual Migration.For some sites we migrated successfully.

    but for some sites we are facing challenges..

    We got the update from Microsoft for repairing database and repairing orphan sites..

    We repaired the database and then we got one orphan site and we deleted the orphan sites

    now we are getting the orphan sites count is 0.

    Then we run prescan.exe.

    We got the following error in the log file.

    05/30/2007 12:05:59 Restoring quota and locks on SPSite 97eb08dc-8acd-4fc8-9d54-6acfcc1a63db

    05/30/2007 12:05:59 Checking if Server="I-SHARE1";Database="more2_SITE";Trusted_Connection=yes;App=" prescan.exe" is a WSS V2 SP2 database.

    05/30/2007 12:05:59 Checking if any site has not yet been scanned in Server="I-SHARE1";Database="more2_SITE";Trusted_Connection=yes;App="prescan.exe".

    05/30/2007 12:05:59 Error: The following site has not been scanned. Id = 97eb08dc-8acd-4fc8-9d54-6acfcc1a63db and Url = /sites/ps

    05/30/2007 12:05:59 Checking if any list has not yet been scrubbed in Server="I-SHARE1";Database="more2_SITE";Trusted_Connection=yes;App=" prescan.exe".

    05/30/2007 12:05:59 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.

    Do you have any wonderful idea how to make it work…

    Thanks,

    Rahul.

  55. rahul says:

    Hi William,

    Still we are facing the same issue.

    even after detaching and reattaching the database and cleaning all the orphan sites.

  56. rahul says:

    William,

    Thanks for response.

    We contacted Microsoft Technical Support.

    They solved the issue.

    Thanks,

    Rahul

  57. Gordon Hickley says:

    I have this error message when I attempt to Add a Content database either using STSADM or through the Central Admin:

    "The pre-upgrade scan tool has not yet been run on this database SPContentDatabase.."

    The prescan has been successfully run on the database on a SPS 2003 server, the database has then been detached and attached to a new SQL Server 2005 database server and the failure occurs when attempting to add to a new MOSS web application. The existing SPS 2003 and SQL Server 2000 is not being used.

  58. paul says:

    Hi Bill

    A prescan error:

    06/13/2007 17:35:59 Querying SPSite quota and locks on eb21f665-49ad-4e55-bc38-ecb99c9e8eb5

    06/13/2007 17:35:59 Error: Could not get usage info for SPSite: http://theurl

    06/13/2007 17:35:59 System.ArgumentException: The parameter is incorrect.

      at Microsoft.SharePoint.Library.SPRequestInternalClass.GetSiteItemSizes(String bstrUrl, UInt32 dwItemType, UInt32 dwSortFlags, UInt32 dwTopN, Object& pvarSizeDataSet)

      at Microsoft.SharePoint.Library.a.a(String A_0, UInt32 A_1, UInt32 A_2, UInt32 A_3, Object& A_4)

      at Microsoft.SharePoint.SPSite.get_Usage()

      at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPSiteCore(SPVirtualServer vs, SPSite site, String connectionString)

    Any help would be most appreciated…

  59. Michael Scott says:

    William,

    Very nice tips on upgrade errors!

    I do have a question about the error:

    [UpgradeDiscussionLists] [3.0.87.0] [ERROR] [6/13/2007 9:21:25 PM]: Item update failed for list 85dee5b4-1dd5-449b-b5d3-c57447477854, thread 20061204-1822-02f4-b937-72bfa08c54b3, ordering 20061204135054

    [UpgradeDiscussionLists] [3.0.87.0] [ERROR] [6/13/2007 9:21:25 PM]: Data is Null. This method or property cannot be called on Null values.

    In your tips, you instruct to use the list id to locate the list on a site, but I am not sure how to find it.  Can you describe how to do this?

    Thanks for all the help!

  60. JKK says:

    I’m still getting "There is no Web named "/<path>/<site>"." issues despite running the repair database utility. The missing sites don’t appear in the sites orweb tables, so I’m not sure how prescan is finding them.

  61. JKK says:

    Ignore that last comment its working now

  62. Christopher Bermingham says:

    William, in regards to the ‘Cannot locate the list definition required for upgrade’ error-  We are running into this from sites that do have  custom templates… Is there anything we should be looking for beyond  making sure that all instantiated lists have an associated V2 list template?

  63. mandarin says:

    This is my first prescan. Can someone have a look?

    06/20/2007 10:38:32 Error: Exception while looping through virtual servers.

    06/20/2007 10:38:32 System.MissingMethodException: Method not found: System.String Microsoft.SharePoint.Administration.SPVirtualServerConfig.get_DefaultZoneOutgoingUrl().

      at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneVirtualServer(SPVirtualServer curVS)

      at Microsoft.SharePoint.PreupgradeReport.Scan.Run(StringCollection argsList)

    06/20/2007 10:38:33 Scan finished with failure.

    06/20/2007 10:38:33 ===============================Logs===============================

    06/20/2007 10:38:33 Log file: C:DOCUME~1ADMINI~1.CGILOCALS~1Temp1PreupgradeReport_633179327102676592_Log.txt

    06/20/2007 10:38:33 Summary file: C:DOCUME~1ADMINI~1.CGILOCALS~1Temp1PreupgradeReport_633179327102676592_Summary.xml

    06/20/2007 10:38:33 ==============================Totals==============================

    06/20/2007 10:38:33 Number of sites skipped (already scanned):   0

    06/20/2007 10:38:33 Number of sites scanned:   0

    06/20/2007 10:38:33 Number of broken sites:   0

    06/20/2007 10:38:33 Number of webs scanned:   0

    06/20/2007 10:38:33 Number of broken webs:   0

    06/20/2007 10:38:33 Number of webs using custom template:   0

    06/20/2007 10:38:33 Number of pages scanned:   0

    06/20/2007 10:38:33 Number of unghosted pages:   0

  64. Niyaz says:

    Hi Williams

     I delete the site SEPG from the
    http://i-share1:/sites , then i ran the Prescan.exe for that i got the following error. I knew this sites located somewhere in the database but iam not able to recognize  to delete.

    plz help me

    Error: Cannot get content database Id for SPSite:
    http://i-share1/sites/SEPG

    06/23/2007 13:21:31 Microsoft.SharePoint.SPException: There is no Web named "/sites/SEPG". —> System.Runtime.InteropServices.COMException (0x81070504): There is no Web named "/sites/SEPG".

      at Microsoft.SharePoint.Library.SPRequestInternalClass.OpenSite(String bstrUrl, Boolean bGetUrlOnly, String& pbstrServerRelativeUrl, Guid& pgSiteId, Int32& pOwnerID, Int32& pSecondaryContactID, DateTime& pdtLastContentChange, DateTime& pdtLastSecurityChange)

      at Microsoft.SharePoint.Library.a.a(String A_0, Boolean A_1, String& A_2, Guid& A_3, Int32& A_4, Int32& A_5, DateTime& A_6, DateTime& A_7)

      — End of inner exception stack trace —

  65. Dave says:

    Here are a few of the first lines of my log where the errors are. Hope someone can help me ???

    Error: Cannot load config file: preupgradescanconfig.xml

    06/28/2007 10:36:49 System.IO.FileNotFoundException: Could not find file "C:Documents and Settingsdavemorpreupgradescanconfig.xml".

    File name: "C:Documents and Settingsdavemorpreupgradescanconfig.xml"

      at System.IO.__Error.WinIOError(Int32 errorCode, String str)

  66. Mitja says:

    Thank you for the helpful post.

    But on some sites we still get some errors.

    I have the same error as Mr. Rahul had in previous post.

    Error: The following site has not been scanned. Id = f4df6ba9-2f7e-4455-8f3b-63ca0a43fgff and Url = /sites/wss

    I check for orphans, but the result is zero.

    Any advice would be very helpful.

    Thank you in advance.

  67. Mitja says:

    Hi William,

    i found the problematic site id DB, Sites table. It point to an virtual server that does not exist enymore.

    Is there any problem if i delete this record from Sites table?

    I cannot delete it with stsadm becouse it says that the site does not exist

    Thank you,

    Mitja

  68. Mitja says:

    Hi William,

    the prescan tool completed succesfuly.

    I had the following errors:

    Error: Cannot get content database Id.

    07/05/2007 11:18:40 System.IO.FileNotFoundException: The Web site that is referenced here is not in the configuration database.

    and

    Error: The following site has not been scanned. Id = f4df6ba9-2f7e-4455-8f3b-63ca0a58adeb and Url = /sites/wss

    Than i deleted ID=f4d… entry from Sites table in the content db,

    entry from Webs table with SiteID=f4d…

    and also entries from users table where SiteID was f4d….

    I check all others tables for similar entries but none was found.

    The prescan tool now completes succesfuly, i hope for no further problems with the content DB migration on WSS3.0 and than on Moss2007;)

    Best regards,Mitja