WCF problem with uploading large file, hosted in IIS

Question

I am trying to upload large files to a WCF Service hosted in IIS.

I am using Restful and Streaming method.

But I am not able to upload files which is more than 64KB.

I tried lot by changing all the size-related elements in web.config file, but failed to fix the issue.

Here is my code and config, please let me know if anyone find any issues in the code and how can I fix.

Operation Contract

[OperationContract]
[WebInvoke(UriTemplate = "/UploadImage/{filename}")]
bool UploadImage(string filename, Stream image);

Implementation of Operation Contract

public bool UploadImage(string filename, Stream image)
{
    try
    {
        string strFileName = ConfigurationManager.AppSettings["UploadDrectory"].ToString() + filename;

        FileStream fileStream = null;
        using (fileStream = new FileStream(strFileName, FileMode.Create, FileAccess.Write, FileShare.None))
        {
            const int bufferLen = 1024;
            byte[] buffer = new byte[bufferLen];
            int count = 0;
            while ((count = image.Read(buffer, 0, bufferLen)) > 0)
            {
                fileStream.Write(buffer, 0, count);
            }
            fileStream.Close();
            image.Close();
        }

        return true;
    }
    catch (Exception ex)
    {
        return false;
    }
}

web.config

  <system.serviceModel>
    <services>
      <service name="Service" behaviorConfiguration="ServiceBehavior">
        <endpoint address="http://localhost/WCFService1" behaviorConfiguration="web"
                  binding="webHttpBinding" bindingConfiguration="webBinding"
                  contract="IService">
          <identity>
            <dns value="localhost"/>
          </identity>
        </endpoint>
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
      </service>
    </services>
    <bindings>
      <webHttpBinding>
        <binding name="webBinding"
            transferMode="Streamed"
            maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"
            openTimeout="00:25:00" closeTimeout="00:25:00" sendTimeout="00:25:00" 
            receiveTimeout="00:25:00" >
        </binding>
      </webHttpBinding>
    </bindings>
    <behaviors>
      <serviceBehaviors>
        <behavior name="ServiceBehavior">
          <serviceMetadata httpGetEnabled="true"/>
          <serviceDebug includeExceptionDetailInFaults="false"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>

and

<httpRuntime maxRequestLength="2097151"/>

Service is hosted in hosted in IIS

Client side Code (console application)

private static void UploadImage()
{
    string filePath = @"F:\Sharath\TestImage\TextFiles\SampleText2.txt";
    string filename = Path.GetFileName(filePath);

    string url = "http://localhost/WCFService1/Service.svc/";
    HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url + "UploadImage/" + filename);

    request.Accept = "text/xml";
    request.Method = "POST";
    request.ContentType = "txt/plain";

    FileStream fst = File.Open(filePath, FileMode.Open);
    long imgLn = fst.Length;
    fst.Close();
    request.ContentLength = imgLn;

    using (Stream fileStream = File.OpenRead(filePath))
    using (Stream requestStream = request.GetRequestStream())
    {
            int bufferSize = 1024;
            byte[] buffer = new byte[bufferSize];
            int byteCount = 0;
            while ((byteCount = fileStream.Read(buffer, 0, bufferSize)) > 0)
            {
                requestStream.Write(buffer, 0, byteCount);
            }
    }

    string result;

    using (WebResponse response = request.GetResponse())
    using (StreamReader reader = new StreamReader(response.GetResponseStream()))
    {
            result = reader.ReadToEnd();
    }

    Console.WriteLine(result);
}

With this much of code I am able to upload 64KB of file, but when I try to upload a file of more than 64KB in size, I am getting error like,

The remote server returned an error: (400) Bad Request

i did what you told but still I am getting same problem, this is how my config looks like now, can you please tell me what is still missing here

<services>
  <service name="Service" behaviorConfiguration="ServiceBehavior">
    <endpoint address="http://localhost/WCFService1" behaviorConfiguration="web"
              binding="webHttpBinding" bindingConfiguration="webBinding"
              contract="IService">
      <identity>
        <dns value="localhost"/>
      </identity>
    </endpoint>
    <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
  </service>
</services>
<bindings>
  <webHttpBinding>
    <binding transferMode="Streamed"
             maxBufferSize="2147483647" maxReceivedMessageSize="2147483647"
             openTimeout="00:25:00" closeTimeout="00:25:00" sendTimeout="00:25:00" receiveTimeout="00:25:00"
             name="webBinding">
      <readerQuotas maxDepth="64" 
                    maxStringContentLength="2147483647" 
                    maxArrayLength="2147483647" 
                    maxBytesPerRead="2147483647" 
                    maxNameTableCharCount="2147483647"/>
    </binding>
  </webHttpBinding>
</bindings>

any final solution with full source code sample working about it ? — Kiquenet
– Kiquenet, Commented Jul 15, 2013 at 6:36

WaseemM · Accepted Answer · 2011-08-02 05:19:13Z

23

The large data transfer issue with wcf:

I have wcf 4.0 service hosted on IIS 7, windows 2008 server. When I call my service with small data say 4K or 5K bytes then request get processed easily but while trying to upload large size it gave me following errors

Bad Request 400
File not found 404 13 as seen in IIS 7 logs
There is no end point listening to the service "myservice url"

In all caseses I was able to transfer small data request with my client application to server but for large size message. Request failed.

I have tried all methods available to solve this issues but nothing worked for me.

After a scratching my head for a week and reading all articles and blogs finally I figured following

<configuration>
<system.serviceModel>
<bindings>
<basicHttpBinding>
        <binding name="myBinding" closeTimeout="00:10:00" maxBufferPoolSize="250000000" maxReceivedMessageSize="250000000" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" messageEncoding="Text">
        <readerQuotas maxDepth="4500000" maxStringContentLength="4500000" maxBytesPerRead="40960000" maxNameTableCharCount="250000000" maxArrayLength="4500000"/>
            </basicHttpBinding>
        </bindings>
    </system.serviceModel>
</configuration>



<system.web>

    <httpRuntime executionTimeout="4800" maxRequestLength="500000000"/>
</system.web>

<system.webServer>
        <security>
            <requestFiltering>
                <requestLimits maxAllowedContentLength="500000000"></requestLimits>
            </requestFiltering>
        </security>
</system.webServer>

<!-- other useful setting -->

<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

So I think It may help someone days....

answered Aug 2, 2011 at 5:19

WaseemM

2311 silver badge3 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

maggix Over a year ago

There only one information left: the service name should be in the form of "YourNamespace.Classname" of the .svc file. Thank you for posting these informations.

Sandepku Over a year ago

dont know how to thank you.. i too had the same issue.. now it works like a charm

DevDave Over a year ago

Are the system.web and system.webserver settings also applicable to a Windows Forms Applcation, anyone? I am also doing large file transfers but using Windows Forms Application

Kiquenet Over a year ago

any final solution with full source code sample working about it ?

zukanta Over a year ago

Thanks for this answer. But Just maybe to clarify things a little as to which of the params needs to get increased. For us we only had to bump up the maxStringContentLength param for things to go thru.

|

amit · Accepted Answer · 2011-06-11 18:58:51Z

2

Based on the size mentioned by you, it seems error due to limit hit at the binding level i.e. readerQuota values. You can confirm if denial of server is due to exceeding the limit at binding level by capturing WCF traces. We can't see the configuration you've posted so, providing our best guess besed on information which is visible.

I'd capture WCF traces at verbose level to troubleshoot the issue.

Btw, have you tried increasing maxRequestLength? http://msdn.microsoft.com/en-us/library/system.web.configuration.httpruntimesection.maxrequestlength.aspx

HTH, Amit Bhatia

answered Jun 11, 2011 at 18:58

amit

2,12316 silver badges10 bronze badges

Comments

tridy · Accepted Answer · 2014-06-27 07:22:32Z

2

what fixed 404 size of the message too big problem for me was a part of WaseemM's example:

<system.webServer>
    <security>
        <requestFiltering>
            <requestLimits maxAllowedContentLength="500000000"></requestLimits>
        </requestFiltering>
    </security>

answered Jun 27, 2014 at 7:22

tridy

1,3341 gold badge14 silver badges24 bronze badges

Comments

Chandrachur · Accepted Answer · 2014-09-16 02:56:34Z

1

See...all of us who are facing this problem of 64KB upload thingy are missing the very basic point. We are setting high values for maxAllowedContentLength, maxReceivedMessageSize...blah blah but still nothing works :). We all miss the very basic point(...well at least I was) is no matter whatever binding configuration we set, are we anywhere mentioning that our ENDPOINT SHOULD FOLLOW THE BINDING CONFIG????...no where...So basically we must let the ENDPOINT know that it must follow our BINDING CONFIG.

<endpoint address="" 
 binding="webHttpBinding" 
 behaviorConfiguration="Your behaviour config name"
 bindingConfiguration="YOUR BINDING CONFIG NAME"
 contract="Your contract service"  />

answered Sep 16, 2014 at 2:56

Chandrachur

5751 gold badge4 silver badges2 bronze badges

Comments

Gilad · Accepted Answer · 2011-06-12 08:52:19Z

0

If transferring large data is if your task you should use MTOM. Just search for "MTOM WCF".

answered Jun 12, 2011 at 8:52

Gilad

2,8965 gold badges30 silver badges41 bronze badges

1 Comment

Kiquenet Over a year ago

any final solution with full source code sample working about it ? I get errors using MTOM and big file

Nathan Tuggy · Accepted Answer · 2014-12-15 01:40:16Z

0

Chandrachur is correct, whatever you specify in your <binding/> or <readerQuotas/>, you need to add "bindingConfiguration="my binding config name" in your <endpoint/>. Otherwise it won't work even if your binding config is correct. you need to make sure your configs are applied to your endpoint. to do so, you need "bindingConfiguration" set correctly.

edited Dec 15, 2014 at 1:40

Nathan Tuggy

2,23727 gold badges33 silver badges38 bronze badges

answered Dec 15, 2014 at 0:58

user4360707

1

Collectives™ on Stack Overflow

WCF problem with uploading large file, hosted in IIS

6 Answers 6

6 Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

6 Comments

Comments

Comments

Comments

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related