Bill Baer /bɛːr/

Ghosted and unghosted pages are references not new to Microsoft Office SharePoint Server 2007, but have received increased interest as a result of their impact on upgrading from previous versions and more recently, the ability to manage pages in an unghosted state. Introduction Ghosted is the preferred state of pages in a site collection, ghosted pages refer to site definition files cached in memory on the server at process startup of IIS.

I’ve updated my post Understanding PRESCAN.EXE Errors to include new errors and solutions. Read more here: http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx. Excerpt: ““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.””

I’ve updated my post Understanding PRESCAN.EXE Errors to include two new errors and solutions. Read more here: http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

MSDN Windows SharePoint Services Run the pre-upgrade scan tool (Windows SharePoint Services) http://technet2.microsoft.com/windowsserver/WSS/en/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx Issues that are reported by the pre-upgrade scan tool http://technet2.microsoft.com/Office/en-us/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx#section1 Install and run the pre-upgrade scan tool http://technet2.microsoft.com/Office/en-us/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx#section2 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” http://support.microsoft.com/kb/923904 Office SharePoint Server Run the pre-upgrade scan tool (Office SharePoint Server)

I’ve made several updates and revisions to my previous post “Understanding PRESCAN.EXE Errors”, I hope this information will be useful in diagnosing and remediating errors generated by PRESCAN.EXE.

*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 “//”. The Content Database contains one or more orphaned Webs.

Prior to upgrading to Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0 one of the prerequisites some of you may have already noticed is running PRESCAN.EXE from the installation directory. This post will hopefully provide some insight into PRESCAN.EXE as well as best practices on when it should be run. PRESCAN.EXE has two primary purposes: It parses and saves List definitions with the associated Lists. SharePoint Portal Server 2003 Service Pack 2 already incorporates this feature whenever a list is modified; however, this process should be completed for all Lists, so prescan calls the SharePoint Portal Server 2003 Service Pack 2 method to persist that data.