Home     Products      Support      Corporate     Sign In 
Support Knowledge Base, Article 900
Large uploads fail in ASP with IIS 6.0
When uploading large files to an ASP page on an IIS 6.0 server, the temp files are created but never saved or IIS returns a 403 error response.

For IIS6.0 users, the AspMaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of an ASP request. If a Content-Length header is present and specifies an amount of data greater than the value of AspMaxRequestEntityAllowed, IIS may return a 403 error response.

You may also experience a scenario when transferring multiple files where no error is returned. Instead any file which is sent after the AspMaxRequestEntityAllowed value is exceeded for the entire upload will not be saved. The temp files will be created in the Path directory for all files in the transfer, but they will not be saved.

In order to solve this problem and increase the AspMaxRequestEntityAllowed value, open your Metabase.XML which is located in c:\Windows\System32\Inetsrv. The simplest way to edit it is with Notepad. Find the line "AspMaxRequestEntityAllowed" and change it a sufficiently large value to account for your transfers. For example, 1073741824 (1GB) would be high enough in many cases.

If you want to edit the Metabase.XML file while your IIS server is running, you need to set a special property in your IIS Manager.

  1. In IIS Manager, right-click the local computer, and then click Properties.
  2. Select the Enable Direct Metabase Edit check box. Enabling Direct Metabase Edit changes the EnableEditWhileRunning property from 0 (FALSE) to 1 (TRUE).
To edit the Metabase.XML without making any changes to your IIS server, stop the IIS server with the IISRESET /STOP command and make your changes, then use the IISRESET /START command to restart the server.

Created : 8/12/2004 2:46:17 PM (last modified : 8/12/2004 2:46:17 PM)
Rate this article!