?
Solved

SharePoint InfoPath Timeout Question

Posted on 2013-10-25
1
Medium Priority
?
1,031 Views
Last Modified: 2013-10-30
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
0
Comment
Question by:jkeagle13
1 Comment
 
LVL 28

Accepted Solution

by:
clayfox earned 2000 total points
ID: 39600586
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

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Note:  There are two main ways to deploy InfoPath forms:  Server-side and directly through the SharePoint site.  Deploying a server-side InfoPath form means the form is approved by the Administrator, thus allowing greater functionality in the form. …
A while back, I ran into a situation where I was trying to use the calculated columns feature in SharePoint 2013 to do some simple math using values in two lists. Between certain data types not being accessible, and also with trying to make a one to…
Integration Management Part 2
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…
Suggested Courses

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question