Translate

Tuesday, February 10, 2015

Unable to parse page for field values: The 'mso:CustomDocumentProperties' start tag on line 2 does not match the end tag of


When you have upgraded from SP 2007 to SP 2010 and trying to access customized any .aspx pages you might receive the the below errors - 


1. List does not exist.  The page you selected contains a list that does not exist.  It may have been deleted by another user.

2.w3wp.exe (0x5C30) 0x62A8 SharePoint Foundation Performance btw0 Medium Unable to parse page for field values: The 'mso:CustomDocumentProperties' start tag on line 2 does not match the end tag of 'mso:PSD_x0020_Product_x0020_Mgr'. Line 354, position 7., pageContent = 

3. System.ArgumentException: Value does not fall within the expected range.
Unexpected       System.ArgumentException: Value does not fall within the expected range.    at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback ...   b38ad70a-09d7-420e-b3fc-d91ebbff39d9

You can try the below steps - 

1) Deactivate the features - publishing
2) delete the "Relationships List"
3) Activate the features using PowerShell. It creates the  "Relationships List" again

Or 
you can also try to copy the problematic .aspx page from explorer view and paste at the same location with different name and then browse it.

seems the below tag is automatically updated in copied page and it works -

<mso:_dlc_DocIdItemGuid msdt:dt="string">620c31d7-5d91-40d2-9c60-d08101fcc0d8</mso:_dlc_DocIdItemGuid>

Note - this is in my case so please first check the situation and error and then try these above options.

Thank you !

No comments:

Post a Comment