Share [My] Point provides insights from Deon Taylor into business solutions for Information and Knowledge workers in and around SharePoint (MOSS and WSS) and related technologies.

Sunday, April 15, 2007

Prescan.exe finished with failure

We have started a large upgrade SPS 2003 to MOSS 2007 project for one of our customers. The approach we are taking is to the content database migration upgrade. As confusing as anything with the words migration and upgrade joined together may sound, there is a logic to the approach over the other ways of completing the upgrade, which I will get to later.

An important first step in the upgrade is to run the prescan.exe over your SPS 2003 environment and content database.

On the source SharePoint Portal Server, run the Office SharePoint Server 2007 Prescan utility. You will need to copy the following files from a base MOSS installation (i.e. from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN)

Prescan.exe

PREUPGRADESCANCONFIG.XML (if you have created custom site definitions in SPS 2003, then update this file)

2. Once you have the hotfix, follow the steps on this KB http://support.microsoft.com/kb/918744• To detect orphaned items, use the following command line:stsadm -o databaserepair -url http://URLofWindowsSharePointServicesSite -databasename DatabaseName• To delete orphaned items, use the following command line:stsadm -o databaserepair -url http://URLofWindowsSharePointServicesSite -databasename DatabaseName -deletecorruption

3. This resolved all my issues but one.To resolve my last issue also involved using the stsadm command line.In this case I used it to delete the site /test/jr with the following syntax: