InfoPath Form Services Publish: "The SOAP message cannot be parsed"

Question

We are trying to publish a basic InfoPath Forms Services form for list with a very large number of columns - we think this might be the problem, but not sure. Here is the publish error:

"The SOAP message cannot be parsed"

Here is the data from the ULS log:

03/07/2013 11:05:03.86  w3wp.exe (0x042C)                           0x1690  InfoPath Forms Services         Runtime                         42fc    High        Can't parse solution ID:    f2d89f42-be70-4bcc-a4a1-f8736ef7ac84
03/07/2013 11:05:03.86  w3wp.exe (0x042C)                           0x1690  InfoPath Forms Services         Runtime                         fvf8    Assert      Form databind failed: There has been a critical error while processing the form. StackTrace:   at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Control.AddedControl(Control control, Int32 index)     at Microsoft.Office.InfoPath.Server.Controls.WebUI.BrowserFormWebPart.AssignFiles(Boolean ignorePostbackDataOnInit)     at Microsoft.Office.InfoPath.Server.Controls.WebUI.BrowserFormWebPart.EnsureDataBinding()     at System.Web.UI.Control.OnPreRender(EventArgs e)     at Microsoft.SharePoint.WebPartPages.WebPart.OnPreRender(EventArgs e)     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.... f2d89f42-be70-4bcc-a4a1-f8736ef7ac84
03/07/2013 11:05:03.86* w3wp.exe (0x042C)                           0x1690  InfoPath Forms Services         Runtime                         fvf8    Assert      ...UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Control.PreRenderRecursiveInternal()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)     at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)     at System.Web.HttpApplication.BeginProcessRequestNotificati...  f2d89f42-be70-4bcc-a4a1-f8736ef7ac84
03/07/2013 11:05:03.86* w3wp.exe (0x042C)                           0x1690  InfoPath Forms Services         Runtime                         fvf8    Assert      ...on(HttpContext context, AsyncCallback cb)     at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     f2d89f42-be70-4bcc-a4a1-f8736ef7ac84
03/07/2013 11:05:03.86  w3wp.exe (0x042C)                           0x1690  SharePoint Server               Unified Logging Service         c91s    Monitorable Watson bucket parameters: SharePoint Server 2010, ULSShipAssert12, fvf8, 14.0.6029.0    f2d89f42-be70-4bcc-a4a1-f8736ef7ac84

Does anyone have any idea how to fix this? It appears to be a bug inside InfoPath form services.

Update: deleting the InfoPath Form and reverting back to SharePoint works, but trying to create a new InfoPath forms fails with the same error.

Update: InfoPath works fine on the server and this form was working OK when there was ~60 fields instead of ~180 fields.

Update: I saved the list as (an empty) template and was able to recreate the list and customize it in InfoPath... so it seems it could be also be related to the amount of data in the list as well.

Answer 1

It is confusing what you describe...

• There is no need to delete Infopath form in order to revert to default sharepoint template. It is possible to use both default sharepoint template and Infopath custom template in parallel - for different modes different templates

• Then, if you had not managed to publish the Infopath form template, I do not grasp why and how you revert it...

IMO, it is impossibe to publish Infopath template of Sharepoint List Form if:

• Sharepoint IPFS (Infopath Form services is not available (it is available only in Enterprise Sharepoint server) or if they are not configured/enabled;

• Infopath form template contains incompatible for rendering in browser features

Also, I would have tried to increase the Data Connection Response Size

Update:
I could have also referenced to size and number limits but they are more rigid from sharepoint side and since you probably created the Infopath form from existing sharepoint list by pressing "Customize" button on ribbon, they would have been useless.

Answer 2

Thanks to Daniel Yang on my TechNet post - as I suspected, I need to increase the IIS executionTimeout configuration as per this article.

I will run this after hours and report any issues back.

Update: It worked - I needed to increase the timeout to 6 minutes (360 seconds) for it to work. 240 seconds wasn't enough. Fortunately subsequent saves are faster, but ideally we'll archive off some old items.

Answer 3

I ran into this today. In my case the user had modified the fields outside of InfoPath and this caused the issue. When opening InfoPath there is that message that says fields have modified do you want to update the form. I had to answer NO to that. Then save over the updates the user had made then reapply what they wanted inside the form so that InfoPath was the driver of the updates instead of SharePoint and Infopath arguing with each other.

That worked for me.

Answer 4

Make sure that the InfoPath form Template is not checked out in SPDesigner. This was the problem which I had.