Understanding PRESCAN.EXE in MOSS 2007

Great Office 2007, SharePoint Server 2007 and Windows SharePoint Services V3 beta2

Marwan Tarek Blog — Sat, 03 Jun 2006 12:13:32 GMT

via JOPX
&nbsp;
Ah finally, it is here ... get your Office 2007 beta2 ... So, to get things going -...

re: Understanding PRESCAN.EXE in MOSS 2007

Justin Greywolf — Tue, 06 Jun 2006 01:40:05 GMT

So where can I find some information about running this scan? I have run it a few times, and it keeps failing with the following:

06/05/2006 15:34:43 System.MissingMethodException: Method not found: Void Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(System.String).
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPSiteCore(SPVirtualServer vs, SPSite site)
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPSite(SPVirtualServer vs, SPSite site)
06/05/2006 15:34:43 System.MissingMethodException: Method not found: Void Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateSchemaAllListsOfWeb(System.String).
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPSiteCore(SPVirtualServer vs, SPSite site)
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneSPSite(SPVirtualServer vs, SPSite site)

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Sat, 17 Jun 2006 01:13:19 GMT

Can you provide the command line and swtiches you are using, e.g. /all, /<vs>, etc.in addition to a what your environment looks like, SPS + WSS, WSS only, etc.

re: Understanding PRESCAN.EXE in MOSS 2007

Grayden Husband — Thu, 27 Jul 2006 08:03:34 GMT

Justin Greywolf - did you resolve this issue. I had the same, and found that installing WSS and SPS service packs on my 2003 build BEFORE running the inline upgrade fixed the problem. (No longer got this error - although the upgrade process still doesn't work)

The method UpdateSchemaAllListsOfWeb is in Microsoft.SharePoint.Library version 11.0.0.0 - ie, it's not part of 2007.

cheers.

re: Understanding PRESCAN.EXE in MOSS 2007

Joel Oleson — Fri, 13 Oct 2006 00:09:23 GMT

Nice job Bill. I saw your blog mentioned in a Vorsite article recently.

http://www.vorsite.com/insite_1006_aom.asp

re: Understanding PRESCAN.EXE in MOSS 2007

Angel del Olmo — Tue, 07 Nov 2006 15:00:10 GMT

We have created a portal site in SPS 2003 with name “desarrollo.moss.extranet”. The Virtual server name is “desarrollo.moss.extranet” and is listening in port 80.

When I run prescan.exe the following error is thrown:

“An outbound zone URL is configured for something other than the default zone on virtual server http://desarrollo.moss.extranet/, and no default zone outbound URL is defined. This is not supported, and must be corrected before upgrading.”

The default zone outbound URL IS defined

¿Any ideas?

Thanks

Angel

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Wed, 08 Nov 2006 18:08:07 GMT

I would recommend confirming your Access Setting Information in SharePoint Portal Server Central Administration > Configure Alternate Portal Access Settings, typically http://<server>:<port>/SPS/AccessSettingEdit.aspx. If the server farm is hosting only one virtual server it may be possible to scan using http://<server>/sites/site as opposed to the friendly name.

re: Understanding PRESCAN.EXE in MOSS 2007

Tony Yin — Wed, 29 Nov 2006 20:12:56 GMT

I ran the prescan tool with the following: prescan.exe /c preupgradescanconfig.xml /all

Our env. has 2 WFE network load balanced together, one separate index server.

In the prescan log file, I noticed the following, would you please explain what it means?

11/29/2006 10:41:31 Scanning SPWeb: http://crpvws06d/C0

11/29/2006 10:41:31 Updating list schema in web.

11/29/2006 10:41:31 Cannot locate the list definition required for upgrade. Check to ensure you have all templates and language packs installed.

11/29/2006 10:41:31 Error: Exception scanning web: http://crpvws06d/C0

11/29/2006 10:41:31 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)

also:

11/29/2006 10:42:30 Error: The following site has not been scanned. Id = ac8ae79c-8a72-470f-aa71-ec952e71ce3b and Url = /personal/sbhatnagar

Also:

11/29/2006 10:42:30 Error: The following list has not been scrubbed: Id=949d965f-7958-4799-9df6-5772c9c9a8e5, Name=Document Library, Containing Web=C3

Also in the prescan.log, I see the following:

0 11/29 10:41:31 2368 FAILED to persist field schema of lists in web "http://crpvws06d/C0"

0 11/29 10:41:31 2368 Cannot complete this action.

Please try again.

Your help will be greatly appreciated. Thanks.

re: Understanding PRESCAN.EXE in MOSS 2007

stacey.bailey — Wed, 20 Dec 2006 20:55:52 GMT

I was hoping when I found your post, that it would help me to interpret the pre-scan results. Would you mind sharing insights or pointing us in the right direction to help us understand what the pre-scan messages mean and what types of situations may cause the errors or issues reported?

For example, what does it mean "The following list has not been scrubbed:" What situations would cause a list not to be scrubbed? What action should we take as a result of this message?

Thanks.

PRESCAN Errors: What they mean.

William Baer — Sat, 23 Dec 2006 02:26:23 GMT

I put together this post as a follow-up to my initial PRESCAN topic " Understanding PRESCAN.EXE in MOSS

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Thu, 04 Jan 2007 19:14:53 GMT

In response to Stacey's comment; if a List is orhaned and cannot be reached through the SharePoint OM, prescan will generate the error: "The following list has not been scrubbed", and will include the List Id to additional troubleshooting. For additional information on remediating this and other PRESCAN errors, see my post here: http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx.

PRESCAN Support and Resources for Windows SharePoint Services and Office SharePoint Server

William Baer — Tue, 09 Jan 2007 18:55:57 GMT

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

re: Understanding PRESCAN.EXE in MOSS 2007

Michael Herman (Parallelspace) — Fri, 02 Feb 2007 17:58:47 GMT

Do you know if prescan.exe can be run against a particular port number?

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

(Prescan.exe doesn't seem to recognize the port when I run the above)

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Sat, 03 Feb 2007 22:44:10 GMT

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:

Host header value, TCP, and SSL port settings in Internet Information Services for the Virtual Server
Value for Virtual Server in the front-end web server HOSTS table (C:\WINDOWS\System32\drivers\ETC\HOSTS)
Alternate portal site URLs
WSS SP2 installed
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~1\MS7C45~1\LOCALS~1\Temp\PreupgradeReport_633060994741085700_Log.txt

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

re: Understanding PRESCAN.EXE in MOSS 2007

MOSS Newbie — Wed, 21 Feb 2007 01:21:41 GMT

I copied over the content database from SQL 2000/SPS2003 and did a restore on my new SQL 2005/MOSS2007. When i try to add the content database from sql 2000/SPS2003, it is asking me to run the prescan.exe tool. But when i run the tool, i get the following error.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>PRESCAN.EXE /ALL

Preupgrade scan failed with the following error:

System.InvalidOperationException: The ConnectionString property has not been ini

tialized.

at System.Data.SqlClient.SqlConnection.Open()

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

at Microsoft.SharePoint.PreupgradeReport.MainLoop.Main(String[] args)

and the log files in the local setting show this

02/20/2007 17:10:33 Error: Failed to get connection string to config db.

02/20/2007 17:10:33 System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.SharePoint.PreupgradeReport.Scan.get_configDbConnectionString()

What am I doing wrong?

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Thu, 22 Feb 2007 17:10:56 GMT

MOSS Newbie

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.

re: Understanding PRESCAN.EXE in MOSS 2007

Marc Molenaar — Thu, 05 Apr 2007 17:22:46 GMT

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?

re: Understanding PRESCAN.EXE in MOSS 2007

pascal — Wed, 02 May 2007 13:22:58 GMT

Hi William,

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 ?

Thanks,

Pascal

re: Understanding PRESCAN.EXE in MOSS 2007

John — Mon, 27 Aug 2007 23:17:02 GMT

Hello,

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).

re: Understanding PRESCAN.EXE in MOSS 2007

Bill Baer — Thu, 30 Aug 2007 17:38:53 GMT

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.

re: Understanding PRESCAN.EXE in MOSS 2007

John — Sun, 02 Sep 2007 00:30:12 GMT

Thanks Bill,

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

Question #1:

Do we run prescan on the 2003 environment first...before restoring it into our new MOSS environment?

Question #2:

Does the precan have to be 100% successful in order to continue with upgrade

Question #3

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!