SharePoint InfoPath Timeout Question

Hello,

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.

Thanks,
Joseph Irvine
jkeagle13Asked:
Who is Participating?
 
Clay FoxConnect With a Mentor Director of Business IntegrationCommented:
I am not aware of another place to impact the timeout.

options I would see
1. Break the form up into multiple linked forms so that each submits quickly.
2. Host the form on a separate site
3. Have them update the timeout, I do not think they would see any other issues unless things timing out is common and purposeful and they do not want that to take longer for the users who experience it often. My opinion is that they are just being lazy or paranoid, if you think about the timeout and what it does, lengthening it a bit is not going to be noticed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.