We believe the problem is caused by the WCF service, namely when you issue such a "large" request, it does require some settings. The allowed request size should be increased on the service side (in the web.config):
Define binding with longer max size:
<binding name="ServicesBinding" maxReceivedMessageSize="4000000" maxBufferSize="4000000">
<readerQuotas maxArrayLength="4000000" maxStringContentLength="4000000"/>
and use it in the service declaration
The used values for these attributes are random and if you need to, they can be increased more. If the problem persist, please use Fiddler proxy
to identify the exact problem that occurs i.e. sniffing the response from the server should give you an idea or exact error.
Hope this information helps
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!