I am running into an issue while uploading a massive InfoPath browser-based SharePoint 2010 form. I receive the error: "SOAP message cannot be parsed" in an Enterprise farm I am working in managed by a different organization.
I went to a dev VM I have built and was able to replicate the same behavior. I stumbled across the following, indicating I should increase the ExecutionTimeout in web.config; which I did: http://binduchinnasamy.blogspot.com/2012/07/soap-message-cannot-be-parsed-error.html
. It worked great; fixing the problem in my dev VM.
So I went back to by Enterprise management group for SharePoint and asked that they increase the value likewise. They refused, indicating that it would have ramifications across the entire farm and process beyond just InfoPath. I have found a few kludgy workarounds, like making the changes on my dev VM, then copying the list over. All of those ultimately take considerable amounts of time. I would ideally like to be able to do hot fixes when requested in the Enterprise environment.
Is there any way to fix this issue, like increasing the ExecutionTimeout, such that it was just scoped to my particular site - or even better, to the particular InfoPath form, so that the Enterprise managers will be willing to consider it? There only argument right now is that because this touches everything, other apps would be impacted and could degrade farm performance. I need a solution that I could convince them would fix this without any negative ramifications. Google hasn't been a whole lot of help.