« Previous Next »

Thread: executionTimeout in IIS 7.0

Last post 03-10-2008 3:03 AM by skumar2003. 4 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (5 items)

Sort Posts:

  • 03-09-2008, 7:31 PM

    executionTimeout in IIS 7.0

    Does IIS 7.0 respond to the executionTimeOut attribute of the <httpRuntime> node (ASP.NET weg.config) or is there a specific setting for IIS in system.Webserver?

    When users attempt to upload large files, and due to their slow upload speeds it takes a lot of time to upload these files I see the following exception message:

    The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3)

     I can upload the same files myself so I know it's not the maxAllowedContentLength setting.

  • 03-09-2008, 11:57 PM In reply to

    Re: executionTimeout in IIS 7.0

    I looked in the serverRuntime in the IIS schema, I didn't see a timeout property per se.  Here is a article that explains all the various values set in the IIS 7 serverRuntime section.  'Nagling' is the only thing that seems to kind of fit, which the value is false.  Hope this helps.

    http://msdn2.microsoft.com/en-us/library/aa347568(VS.85).aspx

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 03-10-2008, 12:22 AM In reply to

    Re: executionTimeout in IIS 7.0

    Steve,

     Thanks for the reply. I don't think nagling is the solution. I'm familiar with the concept of Nagle and this problem is not caused by *not* having Nalging enabled (the default). Either ways, it's to do with reducing the amount of "chatter" on the TCP stack.

    I'm really stuck here. I've spent all of today trying to either set the timeout or reproduce the error and I've not been sucessful.

    I'm now building a client application to send a very large file (it seems IE won't event attempt to upload a file greater than 1.2 (aprox) GB. And due to my fast upload speeds I either need a much larger much or throttle the upload (who would have thought that a fast upload speed would be a curse ::).

    In the mean time, if anyone has ideas about what I can try, please do let me know.

     

    Shiv.

  • 03-10-2008, 2:50 AM In reply to

    Re: executionTimeout in IIS 7.0

    This might be helpful here
    323245 How to upload a file to a Web server in ASP.NET by using Visual Basic .NET
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;323245

    From above KB:

    Upload larger files

    By default, ASP.NET permits only files that are 4,096 kilobytes (KB) (or 4 megabytes [MB]) or less to be uploaded to the Web server. To upload larger files, you must change the maxRequestLength parameter of the <httpRuntime> section in the Web.config file.

    Note When the maxRequestLength attribute is set in the Machine.config file and then a request is posted (for example, a file upload) that exceeds the value of maxRequestLength , a custom error page cannot be displayed. Instead, Microsoft Internet Explorer will display a "Cannot find server or DNS" error message.

    If you want to change this setting for all of the computer and not just this ASP.NET application, you must modify the Machine.config file.

    By default, the <httpRuntime> element is set to the following parameters in the Machine.config file:

    <httpRuntime 
    executionTimeout="90" 
    maxRequestLength="4096"
    useFullyQualifiedRedirectUrl="false" 
    minFreeThreads="8" 
    minLocalRequestFreeThreads="4"
    appRequestQueueLimit="100"
    />
    				 

    The Machine.config file is located in the \ System Root \Microsoft.NET\Framework\ Version Number \Config folder. 
     
    I think you can pretty much use above settings on IIS 7.0 as well.

    HTH.

    ~ Ganesh

  • 03-10-2008, 3:03 AM In reply to

    Re: executionTimeout in IIS 7.0

    Ganesh,

    My issue is not uploading files larger than 4,096. I'm uploading files GBs is size. In IIS 7.0 the maxRequestLength has not purpose/meaning. IIS 7.0 requires a maxAllowedContentLength attribute setting under requestFiltering - requestLimits.

    I've done the above since I'm able to upload files in the GBs. However, I don't see a setting for IIS equivalent to the executionTimeout attribute as mentioned in my original post. So what I need to know is how to set the time out in IIS 7.0.

Page 1 of 1 (5 items)
Microsoft Communities