Web Forms

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

tmarq — Wed, 12 Jul 2006 08:46:45 GMT

The error message “Insufficient system resources exist to complete the requested service.” corresponds to system error code 1450 (ERROR_NO_SYSTEM_RESOURCES). This is HRESULT 0x800705aa.

In 1.1, HttpPostedFile.SaveAs reads the entire posted content into a byte[ ], and then attempts to write that to a file. If the file is on a UNC share and the posted content is larger than approximately 64 MB, we will fail with the error above. This problem was fixed in 2.0, where the posted content is read in chunks when writing it to the file.

You can work around the problem in 1.1 by reading the HttpPostedFile.InputStream one chunk at a time. Write each chunk to a FileStream and flush the FileStream before reading the next chunk from HttpPostedFile.InputStream.

Thanks,

Thomas

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

AndreasGron — Mon, 26 Jun 2006 11:35:35 GMT

I found this link that also discusses the problem

http://weblogs.asp.net/mhawley/archive/2004/05/11/129824.aspx

Quote (Matt Hawley):

First the good...

To upload large files, and not receive the DNS Error or the page stopping while uploading, we found several settings between the machine.config and the web.config files that you need to modify. There are specifically 3 places, 2 of which can be overwritten in your web.config file.

In your web.config, add a line under your system.web <httpRuntime executionTimeout="54000" maxRequestLength="512000" /> where execution timeout is in seconds, and maxRequestLength is in KB. executionTimeout, is basically the amount of time a thread will continue to run, and accept data by IIS/.NET. maxRequestLength, is the total amount of data that can be sent through HTTP Post to the server. The default is 4MB (4096)...and is generally set low so that your server will not be overwhelmed by possible DoS attacks.

In your machine.config, modify responseDeadlockInterval to equal the same amount of time for executionTimeout. responseDeadlockInterval, is basically the amount of time that the Client's browser and Server will continue to communicate. Every several minutes or so, the server polls the client, asking if they have any more information to send, if they do not receive anything back after several times, then the server stops the current thread and all communication is stopped. This is the cause of the DNS Error you may see sometimes.

These 3 changes will allow you to successfully upload large files.

Now...the bad...

Memory deallocation is a major issue, that has no current solution. Whenever you upload files via HTTP Post, the file is stored in the memory of the aspnet_wp.exe process, and never deallocates completely (if your lucky a few MB gets released). One of the config settings for .NET processes, allows them to utilize 60% of physical memory on the server, at which point the process is recycled and all execution is stopped. Whenever a new upload is started, though, some memory is de-allocated, but not enough compared to memory that was used in prior uploads.

Microsoft is aware of this problem, and has assured us that it will be fixed with some upcoming releases of the .NET framework. Some solutions that they suggested to us, was to use Classic ASP, Third Party Components, or Custom Built ISAPI filters. Because of our solution we were using this in, we could do none of the three, so we topped the server out at 2GB of RAM. This has provided us with some breathing room if several people start uploading huge files, and gives us enough time to restart IIS if we start nearing 1.3GB of RAM being used by aspnet_wp.exe.

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

AndreasGron — Mon, 26 Jun 2006 11:13:49 GMT

Thanks, I´ll dig into that support article.

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

AndreasGron — Mon, 26 Jun 2006 11:12:29 GMT

Thanks for the comment.

ASPNET has write-permission on the folder. Also, any file under 60 mb works fine.

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

aspcode.net — Mon, 26 Jun 2006 10:45:23 GMT

Andreas, have you read the MORE INFORMATION chapter on this page

http://support.microsoft.com/default.aspx?scid=kb;EN-US;295626

Basically it says that ASP.NET reads the whole file into memory before saving it to disk. So, yes maxrequestlength gives you some extra possibilities, but the resources are not enough to use all that it seems. While it might not make total sense as your error is "System.IO.IOException: ..." but if I was you I would try some third party component - I think http://www.flesk.net/fleskuploader.aspx works around it somehow but if not - look at third party com components.

Re: System.IO.IOException: Insufficient system resources exist to complete the requested service

saifi_hasan@yahoo.co.in — Mon, 26 Jun 2006 09:53:52 GMT

Do check the write permisssion on the Folder you are trying to save file. Make sure eigther ASPNET/ Everyone/ IUSR_machine name have permission to write on this folder.

System.IO.IOException: Insufficient system resources exist to complete the requested service

AndreasGron — Mon, 26 Jun 2006 06:56:22 GMT

I have a web app where users can upload files to the web server and then get a link back to where they can view them. I'm using an ASP.net application with web interface for uploading

It works great with files up to about 60MB and then I'm getting this error:

System.IO.IOException: Insufficient system resources exist to complete the requested service. at System.IO.__Error.WinIOError(Int32 errorCode, String str) at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count) at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count) at System.Web.HttpPostedFile.SaveAs(String filename) at ASP.Default_aspx.SubmitButton_Click(Object Source, EventArgs e) in C:\Inetpub\Approvals\default.aspx:line 27

with anything larger.

I cant find any reference to that error in any .net related issues (only some with SQL but I'm not using SQL).

I have modified my web.config to allow up to 200MB files (httpRuntime maxrequestlength="200000") and my server timeout (executiontimeout="60")

Any ideas of what's causing this?

Server is running on PIII 2 GHz, Win 2003 server, .Net 1.1, IIS, 1 GB MB RAM with plenty of free hard drive space

Thanks in advance for any comments on this.

/Andreas