Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS 2007 Fails to upgrade some custom and standard SPS2003 areas

  Asked By: Callie    Date: Sep 25    Category: MOSS    Views: 1665

I just wanted to share this information, in the hope that it may save
some of you days of pain in upgrade/migration.
(Perhaps someone might like to blog it too?)

I have run through trial content database migration of a clients' 03
environment many times, finding that many SPS areas did not upgrade
according to the new site definitions and upgrade definition file we
created. The results were that the areas had no welcome pages,
certain MOSS features could not be installed to the sites and often
the underlying data could not be reached. Basically, the areas were
heavily corrupted post upgrade.
We tried in-place and gradual upgrades too, with the same results.

We spent many hours and days checking and re-checking the old and new
site defs, looking for why the upgrade process was not working
correctly.
Almost by chance, we decided to use the SharePoint Explorer tool to
go in and look at the live portals. This tool allows you to browse
(and edit) certain information about the sites and areas in the farm.
One column of information defines the 'Area Template' or 'Site
Template' from which the area/site was created. We noticed that in
some cases, they were empty. We immediate check and found a direct
corrolation between the sites/areas which didn't upgarde and those
that did.
As another pre-upgrade task, it would be prudent to use the
SharePoint Explorer tool (or similar) to check that this information
is populated or (it seems) MOSS does not know how to handle the
areas/sites correctly - even if you have correctly created your new
site and upgrade definitions.
Note: The 'Search' area does not need this information, since it
isn't a real area in SPS and MOSS creates a new search centre anyway.
Try to avoid the temptation of changing anything but this
information, you might break things!

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Allyson Burgess     Answered On: Sep 25

I believe that sites and areas  created before one of the
service packs created this situation. What is the property of the Web
from the API that must be updated to contain some value?

 
Answer #2    Answered By: Vinay Thakur     Answered On: Sep 25

In SharePoint Explorer, the field is 'AreaTemplate' for SPS areas
and 'WebTemplate' for WSS sites.

 




Tagged: