SOAP message cannot be parsed

SharePoint list has 209 columns and there are 9 lookup columns and 19 calculated fields. With this list structure when you re-publish the InfoPath, SharePoint trying to update each item's property behind the scene and this operations times-out is logical with “SOAP message cannot be parsed” error.

To support more execution time override the executionTimeout <httpRuntime maxRequestLength="51200" executionTimeout="3000" /> in related web.config file. I tried with 3000 seconds and the update went through successfully.

Again this can be due to many reason - large list/calculated fields/number of views/applied master page and CSS- so please check your ULS log and Fiddler to get the exact situation.

Thank you !

SharePoint - Maximum Values

SharePoint Boundaries – Maximum Values

SharePoint Thresholds – Maximum Values

SharePoint Supported Limits – Maximum Values

To find all the large lists with items count - PowerShell

I have seen many times you have the immediate requirement of getting the large list for any or all the web apps in your SharePoint farm.

Please run this PowerShell for each content database - Best practice is off production hours 

Use wss_content_relatedDBName

SELECT ItemChildCount + FolderChildCount as Items, DirName +'/' + LeafName as RelativePath FROM alldocs WITH(NOLOCK) WHERE ItemChildCount + FolderChildCount > 5000 ORDER BY Items DESC

Thank you!

SharePoint Designer Performance Issue at the client side

Sometimes i have seen SharePoint performance issue at the client side - this can be due to many reason but you can give a try for below steps at client side and see if this helps you !

1. Close SharePoint Designer.

2. Clear your Internet Explorer's temporary Internet cache and close the browser.

3. Remove content in Folder %System Drive%\Users\%user%\AppData\Local\Microsoft\WebSiteCache).

4. Type %temp% at a run prompt and delete all the temp files in there.

5. Type temp at a run prompt and delete all the temp files in there.

6. Delete %APPDATA%\Microsoft\SharePoint Designer\ProxyAssemblyCache

7. Delete the contents of: %APPDATA%\Microsoft\Web Server Extensions\Cache 

8. Delete contents of %USERPROFILE%\AppData\Roaming\Microsoft\SharePoint Designer

you can also check @ server side - change with your URL

$app = Get-SPWebApplication http://abhi.interest.com

$app.ClientCallableSettings.ExecutionTimeout

Try to increase ClientCallableSettings.ExecutionTimeout values - 

$app.ClientCallableSettings.ExecutionTimeout = 5400000000

$app.Update()

Best of LUCK!

ProcDump v7.01

ProcDump is a command-line utility whose primary purpose is monitoring an application for CPU spikes and generating crash dumps during a spike that an administrator or developer can use to determine the cause of the spike. ProcDump also includes hung window monitoring (using the same definition of a window hang that Windows and Task Manager use), unhandled exception monitoring and can generate dumps based on the values of system performance counters. It also can serve as a general process dump utility that you can embed in other scripts.

Download URL- https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

Tiny tool and you can run at client side - I was trying to test the this for SPD with the below syntax

1. Put the binary to c:\
2. Open DOS shell 
3. Use this command for SPD - procdump.exe -f "" -e 1 -w spdesign.exe > proc.txt
4. Open SharePoint Designer and open the site
5. Once done - Ctr+C to terminate the dump collection process
6. Open proc.txt and see the result for further analysis

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 !