Monday, September 12, 2011

SharePoint 2010 RTM Personal View did not refresh the view name from breadcrumb

If you have multiple personal views on the lists or Document libraries, you may change the view using one of the following mechanisms. Change the views from ribbon bar or from breadcrumb.

We have identified there is a “bug” that view name/title does not change if you change it from breadcrumb on SharePoint RTM version. This is causing confusions for lots of end users using personal views. Here are procedures to produce this and way to fix it


1.       Procedure to reproduce it

  • Create a Document library
  • Create one personal view called “View1” with column “File Size”
  • Create another personal view called “View2” with column “Item Child Count”
  • Click “View1” from breadcrumb and it will display items with column “File Size” - this is good and see screen shot below
  • Click “View2” from breadcrumb and it will display items with column “Item Child Count” - this is good also 


  • The breadcrumb still stays to display “View1” even you have selected “View2” - this is bad and see screen shot below


2.       Way to fix it 
We have tried to fix this but since we are upgrading to SP1 + June CU, I test it on upgraded version and 
it seems fixed. The version after SP1 + June CU is 14.0.6106.5002.

If you find any better ways to fix it on RTM version, please share.

Thursday, September 8, 2011

SharePoint 2010 SP1 and June CU Upgrade issue #3 - Broken functions


There are many issues reported by end users on SharePoint 2010 SP1 and June CU you may need to verify on your end. Here is the list of the potential issues for your reference.



1. Security validation error when people picker is on an infopath form.
http://ghamson.wordpress.com/2011/07/20/security-validation-issue-form-services-issue-with-sp1june-2011-cu-release-2-in-sp2010-sharepoint-msproject-projectserver/

 
2. Cannot provision new PWA sites through the GUI. Workaround is to create via powershell.  We have verified this is an issues on SP1 and June CU.
http://projectserverblogs.com/?p=4991

 
3. Unable to open Performance Point Dashboard Designer after SP1/June CU
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/4c71d238-d4ff-4320-833b-47985b36a8e1


4. JS Bug in grouped view since SP1?
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/ea9e87d5-5b5f-408e-a1bc-a6326ef458ad


5. SP 2010 Document Library Column "Show Filter Choices" is not ...
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/70c6cc25-d1c9-42cd-8d3d-463252e4e1f0


6.Sharepoint Wiki Link Creation Failing
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/d03f842b-71ae-492c-b083-2abde53068a9


7. SP2010 Column Filter causing Unable to display Web Part error and ...
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/44cfd798-be7a-4436-8786-bd44049e7def



8. Security validation issue
http://www.infopathdev.com/forums/p/20173/70028.aspx



9. June CU Unique Permissions \ People Picker Issue - This has been confirmed in our environments and Microsoft claimed it will be fixed in August CU.

 
10. Update-SPProfilePhotoStore not working after SP1 + CU June 2011 - We are having issues to import pictures and it is an issue.

 
11. BI status list display form missing source list after upgrade
http://sharepointconnoisseur.blogspot.com/2011/09/sharepoint-2010-sp1-and-june-cu-upgrade_14.html






We will continue to discuss each issue in details in the future. 

Please share any other issues.

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.