SharePoint 2013 executionTimeout value

Question

_{Wednesday, October 7, 2015 2:22 PM}

I was asked by a vendor what our current executionTimeout value is on our onpremise SP2013 farm. When looking at the WFE's web.config I see that some pages have their own setting for this value (all set to 3600) but I do not see a general setting for this. So I'm guessing it is set at the app.config level? Is this so? Where is the app.config kept? If not, where is this value set?

Thanks!

Love them all...regardless. - Buddha

All replies (8)

_{Wednesday, October 7, 2015 4:13 PM ✅Answered}

You would change the executionTimeout value under the parent system.web/httpRuntime element, rather than the nested ones in location elements.

Trevor Seward

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

_{Thursday, October 8, 2015 5:55 AM ✅Answered}

Hi KansasCoder,

According to the MSDN the executionTimeout is a TimeSpan attribute that Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET. The default is 110 seconds.

The SharePoint application pages under the layouts folder uses the web.config file at the following location.

C:\Program Files\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS

The default executionTimeout is 360 sec (6 min). You can change this configuration to increase the timeout.

We can find the Web.config file for the associated web application in: C:\inetpub\wwwroot\wss\VirtualDirectories\port. port is the port number for your web application.

The default executionTimeout is 3600 sec (60 min).

For your reference:

http://www.sharepoint2013.me/Blog/Post/257/Adding-execution-Timeout-valueRequested-time-out-error-while-uploading-large-files-in-SharePoint

Best Regards,

Lisa Chen

TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Wednesday, October 7, 2015 3:49 PM}

Web-based timeouts are handled by web.configs, not app.configs (app.configs are for executables). You would set the value in the web.config.

Trevor Seward

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

_{Wednesday, October 7, 2015 4:12 PM}

Thanks Trevor.

I see multiple entries for "location" which contains a page name and has the executionTimeout value set for it. They are all set for 3600, which I assume is 3600 seconds or 60 minutes.  However, I do not see any generic setting for this property which might indicate a default value for the web application. How can we determine this value?

  <location path="_layouts/UploadEx.aspx">
    <system.web>
      <httpRuntime maxRequestLength="2097151" executionTimeout="3600" />
    </system.web>
  </location>

Love them all...regardless. - Buddha

_{Wednesday, October 7, 2015 5:15 PM}

Well, that's just it. There isn't one.

Love them all...regardless. - Buddha

_{Wednesday, October 7, 2015 5:16 PM}

Add one

Trevor Seward

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

_{Wednesday, October 7, 2015 6:53 PM}

So there is no default? It is set to infinity?

Love them all...regardless. - Buddha

_{Wednesday, October 7, 2015 6:59 PM}

IIS times out after 120 seconds by default.

Generally I would push back on a vendor requesting this, or ask the vendor to tell me the explicit location that needed to have the timeout execution adjusted. This can lead to higher load (e.g. allowing tasks to run longer), but each environment would have to be evaluated for the true impact.

Trevor Seward

This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.