SharePoint 2010 SP1 and June CU Upgrade issue #2 - Content type not found (Id: '0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1')

If you upgrade SharePoint 2010 RTM to SP1 and June CU or any other CU, you might encounter error Feature upgrade incomplete for Feature - Content type not found (Id: '0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1'). 

If you check the logs, there will be many errors indicating features related to publishing features such as PublishingLayouts and PublishingResources.

After debugging this, we have identified this is related to only sites migrated from 2007 with publishing features enabled. We had this issue during 2007 migration to 2010 as described in previous blog. Here are the tips and tricks to work around the issue.

1.       Issue summary - Content type not found during 2010 SP1 and June CU upgrade for sites migrated from 2007 with publishing features enabled

2.       Error in psconfig logs are listed below all point to 'PublishingResources' feature and publishing master page. Please check the ones highlighted in RED.

  

[PSCONFIG] [SPSiteWssSequence2] [INFO] [8/5/2011 11:32:51 AM]: SPSite Url=http://sandbox/sites/testsite

 [PSCONFIG] [SPSiteWssSequence2] [ERROR] [8/5/2011 11:32:51 AM]: Feature upgrade incomplete for Feature

'PublishingResources' (Id: 'aebc918d-b20f-4a11-a1db-9ed84d79c87e') in Site 'http://sandbox/sites/testsite'.

Exception: Content type not found (Id: '0x01004D5A79BAFA4A4576B79C56FF3D0D662D').

[PSCONFIG] [SPSiteWssSequence2] [INFO] [8/5/2011 11:32:51 AM]: SPSite Url= http://sandbox/sites/testsite

[PSCONFIG] [SPSiteWssSequence2] [ERROR] [8/5/2011 11:32:51 AM]: Feature upgrade incomplete for Feature

'PublishingResources' (Id: 'aebc918d-b20f-4a11-a1db-9ed84d79c87e') in Site 'http://sandbox/sites/testsite'.

Exception: Content type not found (Id: '0x01002CF74A4DAE39480396EEA7A4BA2BE5FB').

[PSCONFIG] [SPSiteWssSequence2] [INFO] [8/5/2011 11:32:51 AM]: SPSite Url=http://sbx04/sites/itlegal

[PSCONFIG] [SPSiteWssSequence2] [ERROR] [8/5/2011 11:32:51 AM]: Feature upgrade incomplete for Feature

'PublishingResources' (Id: 'aebc918d-b20f-4a11-a1db-9ed84d79c87e') in Site 'http://sandbox/sites/testsite'.

Exception: Specified argument was out of the range of valid values.

Parameter name: Content type not found (Id: '0x0101000F1C8B9E0EB4BE489F09807B2C53288F0054AD6EF48B9F7B45A142F8173F171BD1').

[PSCONFIG] [SPContentDatabaseSequence] [INFO] [8/5/2011 11:32:53 AM]: SPContentDatabase

Name= WSS_Content_test_sb

[PSCONFIG] [SPContentDatabaseSequence] [ERROR] [8/5/2011 11:32:53 AM]: Found a missing feature Id = [aeb3b47f-5d09-4c99-b563-02c746cc1aae]

[PSCONFIG] [SPContentDatabaseSequence] [INFO] [8/5/2011 11:32:53 AM]: SPContentDatabase

Name=WSS_Content_test_sb

[PSCONFIG] [SPSiteWssSequence2] [ERROR] [8/5/2011 11:39:36 AM]: Feature upgrade incomplete for Feature 

3.      Root cause for this issue.

 Please note the Content type with Id: '0x01004D5A79BAFA4A4576B79C56FF3D0D662D' is Publishing Master Page that is related to PublishingResources feature. We are not sure why this is causing the migration issue and it has been confirmed from Microsoft that some other people have similar issues on this. Since we had this issue before during 2007 to 2010 upgrade, we believe this is still related to deprecated or removed site templates in SharePoint 2010. The following site templates have been either deprecated or removed from 2010.

• Wiki Site
• Site Directory
• Report Center
• Search Center with Tabs
• Search Center 
• Collaboration Portal 
• News Site 

The sites created from  Collaboration Portal that has publishing features enabled had some issues during 2007 to 2010 upgrade as we discovered. Other sites created from different 2007 template may have similar issue and we are not be able to identify the exact way to distinguish them.

 

4.       Workaround to resolve the issue after working with several co-workers my group.

a.       Deactivate the 'PublishingResources' feature

b.      Detach the content db

c.       Attach the content db

d.      Upgrade

e.      Activate the 'PublishingResources' feature

Now you have the workaround to resolve this issue during the upgrade. The question will be how we could identify the sites that will fail in upgrade?

Well, you could list all sites created from 2007 by creation date with 'PublishingResources' feature enabled. This may give you all potential sites that might fail in the upgrade. We are still working with Microsoft to see whether we could have easy way to identify those sites or final solution to fix this issue.

If you have better way to resolve this, please share with us.