- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI have a public facing web server with IIS hosting WCF 3.5. When the request is received, the host turns around and calls another WCF 3.5 service inside the firewall, hosted in a .NET Windows Service.
I started having this problem when a client sends more than 200 objects in the List<t> into one of my methods. I read numerous posts about how to resolve this, but my attempts haven't worked. I get this error: "The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.".
Here is the config in my Web.config for the IIS hosted WCF:
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="OrderBehavior">
<serviceMetadata httpGetEnabled="true" />
<serviceDebug includeExceptionDetailInFa
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<basicHttpBinding>
<binding name="Binding" maxBufferSize="2147483647"
<readerQuotas maxDepth="32" maxStringContentLength="81
</binding>
</basicHttpBinding>
</bindings>
<services>
<service behaviorConfiguration="Ord
<endpoint address="http://nathanj-de
binding="basicHttpBinding"
name="IBSServiceEndpoint" contract="MV.IBS.Service.I
</service>
</services>
</system.serviceModel>
...and here is the section from my app.config in the .NET Windows Service hosted WCF:
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="SecureOrderBehavior"
<serviceMetadata httpGetEnabled="true"/>
<serviceDebug includeExceptionDetailInFa
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<basicHttpBinding>
<binding name="Binding" maxBufferSize="2147483647"
<readerQuotas maxDepth="32" maxStringContentLength="81
<security mode="None">
</security>
</binding>
</basicHttpBinding>
</bindings>
<services>
<service behaviorConfiguration="Sec
<endpoint
address="http://nathanj-de
binding="basicHttpBinding"
bindingConfiguration="Bind
name="IBSServiceEndpoint"
contract="MV.IBS.Service.I
<host>
<baseAddresses>
<add baseAddress="http://nathan
</baseAddresses>
</host>
</service>
</services>
</system.serviceModel>
The IIS (1st) address is http://nathanj-desktop/IBS
The Windows Service (2nd) address (receives request from WCF in IIS) is http://nathanj-desktop:800
I did google searches on this error message and read dozens of articles and tried various things.
IMPORTANT: It seems the problem is between the IIS WCF and the Windows Service WCF, not between the client and IIS. When I set a breakpoint in my .net code hosted in IIS, I get to the breakpoint and the hundreds of List<object>'s are there -- they came in. But when the code calls into the winservice-hosted code, that's when I get the error. But you can see that I have very similar config in the winservice app.config.
Please help.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: PurpleJuicePosted on 2009-08-13 at 16:37:31ID: 25094151
I finally found the solution myself. I had to remove some of the attributes, which were apparently causing the failure. Simplify the binding element to:
47483647" />
<binding name="Binding" maxReceivedMessageSize="21
The other attribute settings on that element were causing it to fail, even though I saw tons of documentation that included those other attributes. And/or the ReaderQuota stuff as well.