"SOAP message cannot be parsed" error message in SharePoint 2010 InfoPath

Scenario:

We had a SharePoint list with 50 columns and list contains 3000+ items. The list grew over period of time, and of course list views set-up in a way that total number of items in a view does not exceed the threshold. We we tried to change the InfoPath and re-publish it, got the following error, but when I delete 3000 items from the same list and try to publish the InfoPath, the updates goes through smoothly. 

Solution:

It looks like when we re-publish the InfoPath, SharePoint trying to update each item's property behind the scene and this operations times-out for List contains larger number of Items. So override the httpruntime executionTimeout from the default value. I tried with 3000 seconds and the update went through successfully.

SharePoint EventViwer Errors and its Solutions

Error 1:

Error Text: 

Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.

Reason:

The ULS log is created in a code path where all control templates are loaded into the web application. This is a onetime process which happens just before showing any UI to the user after an IISReset. The source of the problem looks like a stale control template in the control templates folder while the control itself has been removed from the code base.

Fix:

• Navigate to /14/TEMPLATE/ControlTemplates/TaxonomyPicker.ascx user control
• Open the user control in a text editor and locate the first line
• Find the character string , and replace with a comma ‘,’ (without quotes).
• Find the character string " and replace with a single quote ‘.
• Save the user control

**If above fix does not resolve the error, then rename the TaxonomyPicker.ascx user control to TaxonomyPicker.ascx_broken as SharePoint 2010 does not use this control.

Error 2:

Error Text: 

Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unnecessary system resources. To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.

Additional Data:

Current default super user account: SHAREPOINT\system

Reason:

The issue occurs if we fail to configure object caching properly. Object caching helps SharePoint to efficiently retrieve cached versions of items where possible. SharePoint cannot perform optimally without this being done.

Fix:

• create 2 domain users – superreader (Read permissions) and superuser (account that has Full Control access to the SharePoint databases but is not an application pool account)
• Then run a small power shell command to add these super reader and super user to the desired web applications.

$wa = Get-SPWebApplication http://< server >/

$wa.Properties["portalsuperuseraccount"] = “domain\superuser”

$wa.Properties["portalsuperreaderaccount"] = “domain\superreader”

$wa.Update()

 

Error 3:

Error Text: 

The SharePoint Health Analyzer detected an error.  Drives are running out of free space.
Available drive space is less than twice the value of physical memory. This is dangerous because it does not provide enough room for a full memory dump with continued operation. 

Reason: 

This error (warning) is more for production environments. Its a calculation based on the size of the drive and the available free space. So on a Dev VM you will nearly always see this error. Nothing to worry about. That said I would still keep an error on the available disk space and the total size of the ULS log files.

SHAREPOINT 2013 UPGRADE PROCESS

This model describes the required steps to upgrade from SharePoint Foundation 2010 or SharePoint Server 2010 to SharePoint Foundation 2013 or SharePoint Server 2013. The database-attach method is the only supported method for upgrading from SharePoint 2010 Products to SharePoint 2013 Products. Information about the Business Data Connectivity service application applies to both SharePoint Server 2013 and SharePoint Foundation 2013. Information about all other service applications and about My Sites applies only to SharePoint Server 2013.

I am planning to provide you video tutorial for sharepoint 2010 to sharepoint 2013 upgardation in near future. stay tuned.

For information about 2tier to 3tier migration Please visit : http://sharepointshah.blogspot.in/2012/06/scale-out-sharepoint-2010-farm-from-two.html