Archive for upgrade

SharePoint Upgrade: Prescan.exe

You can download prescan.exe from this link or it can be found at “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN” along with preupgradescanconfig.xml


PreScan is a pre-upgrade scan tool used to scan all Web sites in your environment (by using the /all parameter) or to scan a specific URL (by using the /v <URL> parameter). If you do not supply a scoping parameter, all Web sites will be scanned. The pre-upgrade scan tool takes the following parameters:





Scans all site collections in a server farm.

/v <URL>

Scans all site collections at a specific URL.

/c preupgradescanconfig.xml

Uses the preupgradescanconfig.xml file while scanning. This configuration 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. You must use this parameter when scanning site collections based on SharePoint Portal Server 2003. This parameter has no effect when scanning site collections based on Windows SharePoint Services 2.0.



To run Prescan.exe, perform the following steps:


On the command line, change to the folder that contains the file, and then run the prescan.exe command with the appropriate parameters. For example,


prescan.exe /all or

prescan.exe /c preupgradescanconfig.xml /all or

prescan.exe /c preupgradescanconfig.xml /v http://sps


I will recomend to use the second option.


After successful run, it will generate reports with name PreupgradeReport_uniqueID_Log.txt (where uniqueID is a number string) located in the temp directory on the computer of the user who ran the tool (for example, C:\Documents and Settings\User\Local Settings\Temp or Temp\2).


An example output is:



Number of sites skipped (already scanned):   0

Number of sites scanned:   12

Number of broken sites:   0

Number of webs scanned:   41

Number of broken webs:   0

Number of webs using custom template:   0

Number of pages scanned:   4145

Number of unghosted pages:   40 (0.97% of total).



For errors, check Bill Baer blog:


Comments (2)

Upgrade:You cannot add the same content database more than once to a farm, even on different Web applications



Number of sites are zero after upgrade using database migration technique.  




Each site collection in a content database (including each portal site) has a globally-unique identifier (GUID) associated with it, registered in the configuration database. So, adding the same site collection (or portal) twice to the farm, even in separate Web applications, is not possible. Although the database attach succeeds in this situation, the site collection cannot be started. If you need a duplicate copy of a site collection (or portal) in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm.exe backup and restore operations to copy the site collection over to the other farm. The backup and restore process creates a new GUID for the site collection.


Saved my life 🙂

Comments (2)

« Newer Posts