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:
Typically these issues will manifest as a result of failed STSADM backup and restore sequences, but also can occur at the SQL level.
Depending on the nature and growth of your environment, PRESCAN.EXE is best run one (1) week prior to the production upgrade allowing time to address issues uncovered, and again prior to the upgrade itself to ensure that those previous issues have been resolved in addition to identifying new issues, if any.
You should PRESCAN your databases on a Windows SharePoint Services 2.0/SharePoint Portal Server 2003 farm; attaching a SharePoint Portal Server 2003 Content Database to a Microsoft Office SharePoint Server 2007 server farm will upgrade the database (database migration approach). You cannot reattach a SQL 2005 database to SQL 2000; I would restore any backup of this database to SQL 2000, run PRESCAN, remediate any potential issues, and then attach to the SQL 2005 instance which will upgrade the database schema (SQL) and finally proceed with the upgrade.
Is it possible to check a database if it is really modified by the prescan tool? Is there a tool for that or do I have to open the db and search for some specific tags?
I have a strange problem with my prescan !
If I do this command:
- prescan /all: my portal is not identified like a SPS V2:
"05/02/2007 12:19:34 Skipping virtual server: http://myportal/">http://myportal/. Server state = NeedUpgrade. Most likely this virtual server is not extended with WSS v2."
- prescan http://myportal : it works fine (without any error)
But when I try to do a "addcontentdb" in MOSS2007, I have this error:
"The pre-upgrade scan tool has not yet been run on this database SPContentDatabase Name=GA_MOSS2007_Content 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. "
Do you have any suggestion ?
We are running the prescan and get a number of errors and issues which we have had no luck getting resolved. Any suggestions is greatly appreciated. Thnaks for the help!
1.) Error: Web is using a custom template (id = "10101") which can not be located on the web front end.
2.) Error: The following site has not been scanned. Id = 20148f1c-6f35-44cf-a1d1-5b7900a946d5 and Url = /
3.) Error: The following list has not been scrubbed:
4.) 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 (ran this an there were no orphans)
08/27/2007 13:09:19 Number of sites skipped (already scanned): 0
08/27/2007 13:09:19 Number of sites scanned: 31
08/27/2007 13:09:19 Number of broken sites: 1 (3.23% of total).
08/27/2007 13:09:19 Number of webs scanned: 250
08/27/2007 13:09:19 Number of broken webs: 1 (0.40% of total).
08/27/2007 13:09:19 Number of webs using custom template: 30 (12.00% of total).
08/27/2007 13:09:19 Number of pages scanned: 13000
08/27/2007 13:09:19 Number of unghosted pages: 948 (7.29% of total).
The error indicates you have a site/web that is using a custom site definition/template. I would check the site definition/template for the SiteId 20148f1c-6f35-44cf-a1d1-5b7900a946d5 and ensure you have a suitable upgrade definition in place.
I'm really confused about this whole process. I contacted Microsoft and it sounded somewhat straighforward but still having issues. We decided to stand up a new fresh box with MOSS 2007. We moved over the Content dbase from the 2003 environment and ran the command line:
stsadm.exe -o addcontentdb -url http://myserver:80 -databasename ContentDbase_site -databaseserver myserver
We then received the message:
The pre-upgrade scan tool has not yet been run on this database SPContentDatabase Name=ContentDbase_site 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
Do we run prescan on the 2003 environment first...before restoring it into our new MOSS environment?
Does the precan have to be 100% successful in order to continue with upgrade
These are the directions we received from Microsoft:
It looks like the site is pretty heavily customized, and just running a straight upgrade will definitely crash because it will not be able to recognize the customized templates. The way around this is going to be to do a fresh install of MOSS right alongside of SPS 2003, create a new farm, new Web application, then use the Database Attach method for the upgrade. You have already run the Prescan, so all you would need to do is take a backup of the SPS 2003 content database and attach it in MOSS....
***Note, this is where I am confused because even though we have run prescan on the 2003 environment it's telling me it hasn't been run when trying to attach it to MOSS.
Then depending on what your setup is:
If you are going to be using the same SQL server – you would need to go into the SPS 2003 Central Admin and remove (but do NOT delete) the content database from the old site.
Run the STSADM addcontentdb command.
STSADM –o addcontentdb –url http://yourwebsitename –databasename yourdatabasename –databaseserver yourservername –sitewarning 15000 –sitemax 9000
Your site should be browsable as soon as that gets done running!
So at this point a bit lost and could use some guidance.
Thanks for the help!