Hi,
our intranet is using SharePoint Portal Server 2003 SP2, and runs on
top of SQL Server 2005. We have one custom site definition, which is
used as a template for about 30 SPS areas in our intranet. A MOSS 2007
version of the site definition has been made, and it seems to be fully
functional. The SPS2003 portal is upgraded by the gradual upgrade
method. Everything seems to upgrade successfully except for the areas
that use our custom site definition. Prescan.exe completes without
errors. When running the actual upgrade, SharePoint states that
everything was successful (no errors in upgrade.log either), but the
event log has numerous entries with the following message: ": List
does not exist. The page you selected contains a list that does not
exist. It may have been deleted by another user." This is also the
message we get when trying to load one of the upgraded sites based on
our site definition. The SharePoint log says that it cannot locate the
schema.xml file for the list (the schema.xml file is correctly placed
in the list feature folder on the SharePoint server). All other
upgraded sites are fully functional, and we have no problems creating
new MOSS2007 sites from our new custom site definition. On the broken
sites, we have noticed that the system libraries created by the
publishing feature are actually working just fine.
We believe that our custom upgrade definition file could be the
problem. We tried several different versions of our upgrade definition
file, one of them is shown below. We would be very grateful if anyone
could point us in the right direction regarding the upgrade definition
file. The documentation in the WSS SDK does not help us, and we have
not found any web postings that could help us with our particular
problem.
Best regards,
MHH
******************************* UPGRADE DEFINITION FILE
*********************************************
<Config xmlns="urn:Microsoft.SharePoint.Upgrade">
<WebTemplate FromProductVersion="2" ID="10001" LocaleId="*"
ToSchemaVersion="3">
<Lists>
<!-- Milestones -->
<List FromTemplateId="160" ToFeatureId="00BFEA71-E717-4E80-AA17-
D0C71B360599" v3Type="0x01">
<Source v2List="160"/>
</List>
<!-- Technical Documents -->
<List FromTemplateId="163" ToFeatureId="00BFEA71-E717-4E80-AA17-
D0C71B360596" v3Type="0x0101">
<Source v2List="163"/>
</List>
<!-- Project Log -->
<List FromTemplateId="162" ToFeatureId="00BFEA71-D1CE-42de-9C63-
A44004CE0601" v3Type="0x0104">
<Source v2List="162"/>
</List>
<!-- Administrative Documents -->
<List FromTemplateId="164" ToFeatureId="00BFEA71-E717-4E80-AA17-
D0C71B360597" v3Type="0x0101">
<Source v2List="164"/>
</List>
<!-- Iterations -->
<List FromTemplateId="165" ToFeatureId="00BFEA71-E717-4E80-AA17-
D0C71B360600" v3Type="0x01">
<Source v2List="165"/>
</List>
<!-- Project Tasks -->
<List FromTemplateId="166"
ToFeatureId="00BFEA71-513D-4CA0-96C2-6A47775C0598" v3Type="0x0108">
<Source v2List="166"/>
</List>
</Lists>
<Files>
<File FromPath="1033\SPSCUSTPROJECT\default.aspx"
ToPath="SiteTemplates\SPSCUSTPROJECT\default.aspx"/>
</Files>
<!-- Do we need AppliedWebFeatures for the default lists? -->
<AppliedWebFeatures>
<!-- DocumentLibrary -->
<Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360101"/>
<!-- Publishing feature -->
<Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416"/>
<!-- Navigation feature -->
<Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA"/>
<!-- Team Collaboration feature -->
<Feature ID="00BFEA71-4EA5-48D4-A4AD-7EA5C011ABE5"/>
<!-- Milestones -->
<Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360599"/>
<!-- Tecnical Documents -->
<Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360596"/>
<!-- Project Log -->
<Feature ID="00BFEA71-D1CE-42de-9C63-A44004CE0601"/>
<!-- Administrative Documents -->
<Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360597"/>
<!-- Iterations -->
<Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360600"/>
<!-- Project Tasks -->
<Feature ID="00BFEA71-513D-4CA0-96C2-6A47775C0598"/>
</AppliedWebFeatures>
</WebTemplate>
</Config>