This message occurs even if you have increased the value of MaxStringContentLength.
Solution : Create a "default" binding section in the basicHttpBinding section of the server config file.
<readerQuotas maxDepth="32" maxStringContentLength="102400" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
</binding>
For customBinding, this problem can be solved by adding an attribute maxReceivedMessageSize="524288" to httpTransport directive :
<httpTransport maxReceivedMessageSize="524288"/>
You just saved my day.
ReplyDeleteThanks.
Jan.
You just saved my day too.
ReplyDeleteThanks.
Vincent
Great tip. Setting the maxStringContentLength (in a custom binding) worked on some platforms but not all, so applying a default binding was the solution.
ReplyDeleteThanks.
Boris