Solved

SharePoint InfoPath Timeout Question

Posted on 2013-10-25
1
862 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 500 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

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

I have put this article together as i needed to get all the information that might be available already into one general document that could be referenced once without searching the Internet for the different pieces. I have had a few issues where…
The System Center Operations Manager 2012, known as SCOM, is a part of the Microsoft system center product that provides the user with infrastructure monitoring and application performance monitoring. SCOM monitors:   Windows or UNIX/LinuxNetwo…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

708 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now