The underlying connection was closed

Question

0.00/5 (No votes)

See more:

Hello

I have an application that upload picture from aspx pages. I had aspx pages on my PC that has windows7(IIS7). I moved them in a server that has windows 2003 server(IIS6).

Now when i upload a 50KB picture or some text(about 1 KB) i receive this error message in my .Net App:

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

I changed some settings:

web.config: httpruntime max maxRequestLength to 32768

metabase.xml: AspMaxRequestEntityAllowed to 10000000

But still I receive this error.

I use this code at server side:

byte[] bytes = new byte[Request.InputStream.Length];
Request.InputStream.Read(bytes, 0,(int)Request.InputStream.Length);

And this code at client side:

new WebClient("page address").UploadData(MyPicture);

Posted 11-Jan-10 4:02am

Napster25

Updated 11-Jan-10 21:30pm

Tom Deketelaere

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhishek Sur · Answer 1 · 2010-01-11T22:29:00

Solution 1

I think you need to use
<httpRuntime maxRequestLength="8192" />

Check this lovely article :
http://msdn.microsoft.com/en-us/kb/kb00323245.aspx#XSLTH3150121122120121120120[^]

Cheers
:rose:

Posted 11-Jan-10 22:29pm

Abhishek Sur

Abhishek Sur · Answer 2 · 2010-01-12T09:18:00

Well, Actually I showed how to do this.

Did you read the article I specified. I think you need to modify the Machine.config as it will always override the value with this one.

Normal files in asp.net defaults to 4,096 kilobytes(4MB), if you need larger than this, go to \System Root\Microsoft.NET\Framework\Version Number\Config folder and change

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

To the value you need. I dont think changing to web.config works.

I hope this will solve the issue. :thumbsup: