MOSS 2007 Upgrade Problem Fixed- Pages Does not Exists..Upgrade can not continue


As I am busy with SharePoint 2007 upgrade projects for SharePoint Portal Server 2003 to MOSS 2007 I have lot to share but for now this is what I have for right now.

Scenario

We have almost 20 custom site definitions that were developed for one of our SPS 2003 implementation.  We now have developed all these site definitions for MOSS 2007.  We have developed site definition upgrade files for all of them.  Although we have not tested all of them yet but we have reduced a restored environment to two areas and tested a gradual upgrade.  During the first testing we got this error.

Exception

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Upgrading pages for area at "http://sharepoint/Architecture".

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: ENTER — PortalSiteUpgradeAreaAndListingData::UpgradeOOBPages[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Not detaching landing page from page layout because it is not customized.[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Moving v2 database landing page content and webparts to v3 landing page…

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Error moving landing page "http://sharepoint/Architecture/default.aspx": Folder "Pages" does not exist.. Upgrade cannot continue.

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Upgrade encountered an unexpected error. Halting upgrade…

Microsoft.SharePoint.SPException: Folder "Pages" does not exist. —> System.Runtime.InteropServices.COMException (0x8107021A): Folder "Pages" does not exist.

at Microsoft.SharePoint.Library.SPRequestInternalClass.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

at Microsoft.SharePoint.Library.SPRequest.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

— End of inner exception stack trace —

at Microsoft.SharePoint.Library.SPRequest.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveCopyInternal(String strNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveTo(String newUrl, SPMoveOperations flags)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradeOOBPages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradePages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.Upgrade()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: ENTER — PortalSiteUpgradeAreaAndListingData::PersistProgress

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [INFO] [3/24/2007 10:28:41 PM]: Trying to update UpgradeProgress column with value "InjectListingData" on area "Architecture".

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: EXIT — PortalSiteUpgradeAreaAndListingData::PersistProgress

[SiteSequence] [ERROR] [3/24/2007 10:28:41 PM]: Action 12.0.1.0 of Microsoft.SharePoint.Portal.Upgrade.SiteSequence failed.

[SiteSequence] [ERROR] [3/24/2007 10:28:41 PM]: Folder "Pages" does not exist.

[SiteSequence] [ERROR] [3/24/2007 10:28:41 PM]: at Microsoft.SharePoint.Library.SPRequestInternalClass.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

at Microsoft.SharePoint.Library.SPRequest.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

[SiteSequence] [ERROR] [3/24/2007 10:28:41 PM]: Folder "Pages" does not exist.

[SiteSequence] [ERROR] [3/24/2007 10:28:41 PM]: at Microsoft.SharePoint.Library.SPRequest.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveCopyInternal(String strNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveTo(String newUrl, SPMoveOperations flags)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradeOOBPages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradePages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: Begin Rollback()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: End Rollback()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: Begin Dispose()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: End Dispose()

[PortalSiteUpgradeAreaAndListingData] [12.0.1.0] [DEBUG] [3/24/2007 10:28:41 PM]: Elapsed time: 00:03:34.9236172.

[SPManager] [ERROR] [3/24/2007 10:28:41 PM]: Upgrade [SPSite Url=http://sharepoint] failed. Microsoft.SharePoint.Portal.Upgrade.SiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence.

[SPManager] [ERROR] [3/24/2007 10:28:41 PM]: Folder "Pages" does not exist.

[SPManager] [ERROR] [3/24/2007 10:28:41 PM]: at Microsoft.SharePoint.Library.SPRequest.MoveUrl(String bstrUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveCopyInternal(String strNewUrl, Int32 grf)

at Microsoft.SharePoint.SPFile.MoveTo(String newUrl, SPMoveOperations flags)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradeOOBPages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.UpgradePages(AreaData SPSArea, PublishingWeb CMSArea)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.RunUpgradeLoop1(SPSite site, AreaData SPSArea, Int32 parentPermId)

at Microsoft.SharePoint.Portal.Upgrade.PortalSiteUpgradeAreaAndListingData.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[SPManager] [ERROR] [3/24/2007 10:28:41 PM]: Action 12.0.1.0 of Microsoft.SharePoint.Portal.Upgrade.SiteSequence failed.

[SPManager] [ERROR] [3/24/2007 10:28:41 PM]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)

[SPManager] [DEBUG] [3/24/2007 10:28:41 PM]: Elapsed time upgrading [SPSite Url=http://sharepoint]: 00:05:09.

[SPManager] [DEBUG] [3/24/2007 10:28:41 PM]: Disposing SPSite Url=http://sharepoint.

[SPManager] [INFO] [3/24/2007 10:28:41 PM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=NTSWPort1_SITE_Pair Parent=SPDatabaseServiceInstance to Online.

[SPManager] [INFO] [3/24/2007 10:28:41 PM]: Finished upgrading SPContentDatabase Name=NTSWPort1_SITE_Pair Parent=SPDatabaseServiceInstance.

[SPSiteCollectionMigrator] [DEBUG] [3/24/2007 10:28:42 PM]: Recording contents from site SPSite Url=http://sharepoint to the change log

[SPManager] [DEBUG] [3/24/2007 10:28:51 PM]: Elapsed time migrating [SPMigratableSiteCollection Parent=SPManager]: 00:35:48.1843119.

[SPHierarchyManager] [DEBUG] [3/24/2007 10:28:51 PM]: ——————- Begin Growing Tree ——————-

[SPManager] [DEBUG] [3/24/2007 10:28:51 PM]: CanUpgrade [SPMigratableSiteCollection Parent=SPManager] returned: True.

[SPManager] [DEBUG] [3/24/2007 10:28:51 PM]: CanUpgrade [SPMigratableSiteCollection Parent=SPManager] returned: True.

[SPManager] [DEBUG] [3/24/2007 10:28:51 PM]: NeedsUpgrade [SPMigratableSiteCollection Parent=SPManager] returned: False.

[SPHierarchyManager] [DEBUG] [3/24/2007 10:28:51 PM]: ——————– End Growing Tree ——————–

[SPManager] [INFO] [3/24/2007 10:28:51 PM]: Gradual Upgrade session finishes. root object = SPMigratableSiteCollection Parent=SPManager, recursive = True. 2 errors and 4 warnings encountered.

[SPManager] [DEBUG] [3/24/2007 10:28:51 PM]: Removing exclusive upgrade regkey by setting the mode to none

———————————————————————————————————————————————–

Some point to remember while going for upgrade.

  • Do now upgrade the whole site if you your upgrade size is more than 1 GB simply remove all the areas except  one and upgrade them one by one.   This approach is better.
  • Choose a gradual upgrade process.
  • Copy the matching area definition from the 2007 site templates folder and make the necessary changes. 
  • If you custom site definitions.  A good to develop those as features is to deveop them using 2007 UI and get the Schema.xml using Visual studio Extensions.
  • Develop the features for lists and libraries manually by copying the features from the features directory and replace the schema file.
  • SharePoint 2003 Document libraries are changed to Legacy Document library feature installed in SharePoint 2007.
  • In case your upgrade process fails Revert the site and try again after updating from the steps given below.

If you receive this message check the Area definition that you are updating for the following options.

Things to Consider to Fix this issue

  1. There is no sub area under this area that is using some other template (Upgrade process goes inside the hierarchy and pick up the first sub element under the area and try to upgrade it.  If it fails the process will terminate.
  2. The ID for 2007 Custom Area Definition should have the same ID as Custom 2003 Area Definition. Like if the 2003 has ID of 10037 the new one should be 10037.
  3. This Id should be mentioned in the Site Definition upgrade file under the webtemp tag.
  4. The name of site definition upgrade file should be AreaDefinitionFolderNameUpgrade.xml
  5. The ID should be mentioned in the SiteUpgraderConfigSPS.xml for the welcome layout.xml.

Update (17/4/2007)

Do Double check the Site Definition Upgrade File Tags.  If there is something missing that will cause the same result

Do take a look at the Upgrade.log file placed under local drive:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS folder.

I hope you do not receive this message.  But if you do you have to check the things I have mentioned above.  I will post more as soon as I got time.  Looking forward,

Jerry

RSS Viewer Webpart and Authenticated Feeds


RSS Viewer web part and authenticated feeds VIA

Mark Arend

For my reference in project.

RSS Viewer web part authentication requirements

In B2, configuring the RSS Viewer web part to display an RSS feed from a MOSS site nearly always worked without difficulty.  In B2TR, you may encounter a stubborn error “The RSS webpart does not support authenticated feeds” when trying to display an RSS feed from a MOSS site.  The authentication behavior has changed, to match the original design that was not implemented properly in B2.  RSS Viewer will now only work with Authenticated feeds (default for MOSS) when the MOSS server is setup with Kerberos authentication.  Technical details: In B2, the  machine account was used to access the feed; since this account is part of “All Authenticated Users” most feeds just worked.  However, use of the machine account was considered to pose a security vulnerability.  In B2TR, this was fixed to connect to feeds as anonymous, then delegation support was explicitly added by having ASP.Net negotiate the authentication mechanism.

Changing to Kerberos authentication

1. On the Central Administration page, click Application Management.

2. Under the Application Security section, click Authentication Providers.

3. Click the Default provider, and change Integrated Widows authentication to Negotiate (Kerberos)

If SharePoint and the databases it uses are hosted on the same server, this is the only change required to enable RSS Viewer functionality to RSS feeds hosted by SharePoint.

If the SharePoint databases are hosted by a different server than is hosting SharePoint, further configuration is required to enable Kerberos delegation. This is the recommended scenario for farm deployments. To enable Kerberos delegation for a SharePoint web application, the account used for its application pool identity must be configured as “trusted for delegation” and have an SPN registered (see below). If using Network Services for the AppPool identity, then this applies to the machine account. Otherwise, it applies to the domain account configured for the AppPool identity. The machine account of the database server must also have an SPN registered, although it is not necessary for it to be trusted for delegation. The end-user accounts require neither an SPN nor “trusted for delegation.”

In an AD environment whose Domain Functional Level is set to Windows Server 2003, this level of trust can be focused using Constrained Delegation. This ensures that the delegation trust is only permitted between the SharePoint WFE servers and the correct database server.

SPN

The MSDN article Security Briefs: Credentials and Delegation discusses several topics regarding SPNs and Kerberos delegation that are appropriate for this scenario, including use of the SETSPN and KERBTRAY tools, the "trusted for delegation" attribute, and how to configure Kerberos constrained delegation.

SharePoint 2007 Migration Resources


SharePoint 2003 to 2007 Migration

WSS 3.0 & Sharepoint 2007 Database Migration Strategy Steps For Migrating A Sharepoint 2003 Site

http://ezinearticles.com/?WSS-3.0-andamp;-Sharepoi…

SharePoint Managment

Brief Description: See how to mazimize your business potential with Microsoft solutions. TechNet sessions are learning resources designed to meet the needs of IT professionals.

TechNet Quarter 3 FY07 Downloadable Documents

Content Managment Migration to MOSS 2007 

http://blogs.officezealot.com/hansen/archive/2006/…

Upgrade/Migration to Microsoft Office SharePoint Server 2007 (OLE)

http://joeloleson.spaces.live.com/Blog/cns!B05AD15…

Planning for Migration of SharePoint Portal Server 2003 to MOSS 2007

http://www.abelsolutions.com/web/content/sharepoin…