Click here to Skip to main content
13,769,067 members
Rate this:
Please Sign up or sign in to vote.
See more:
hi friendz,
i am getting the huge amount of data(Contacts) from Sql server..i am getting the following error...


An error occurred while receiving the HTTP response to http://localhost:8732/Design_Time_Addresses/ICloudServices/ContactService/. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

{"The underlying connection was closed: An unexpected error occurred on a receive."}

My wcf web.config file:
<service name="ICloudServices.ContactService">
   <endpoint address="" binding="basicHttpBinding" contract="ICloudServices.IContactService">
       <dns value="localhost" />
   <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
       <add baseAddress="http://localhost:8732/Design_Time_Addresses/ICloudServices/ContactService/" />

      <binding name="basicHttpBindingSettings"  openTimeout="00:01:00" receiveTimeout="05:00:00" sendTimeout="05:00:00" maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" messageEncoding="Text">
        <readerQuotas maxDepth="128" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />
        <dataContractSerializer maxItemsInObjectGraph="2147483647" />

        <!-- To avoid disclosing metadata information,
        set the value below to false and remove the metadata endpoint above before deployment -->
        <serviceMetadata httpGetEnabled="True"/>
        <!-- To receive exception details in faults for debugging purposes,
        set the value below to true.  Set to false before deployment
        to avoid disclosing exception information -->
        <serviceDebug includeExceptionDetailInFaults="False" />

Thanks in advance
Posted 4-Jul-12 2:31am
[no name] 4-Jul-12 7:40am
Are the answers you are getting for a similar question you obviously posted with another account ( not good enough?
Rate this: bad
Please Sign up or sign in to vote.

Solution 2

Here this kind of exception can happen if your receiveTimeout is not large enough.
Here in your configuration, you are setting
in "binding name="basicHttpBindingSettings" " but you are not associating it with your end point.
Either remove the name attribute from the binding so that basicHttpBinding will use it as default binding configuration. Or add
to your basicHttpBinding endpoint. Hope this will work.
Rate this: bad
Please Sign up or sign in to vote.

Solution 1


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

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Cookies | Terms of Service
Web01-2016 | 2.8.181117.1 | Last Updated 6 Jul 2012
Copyright © CodeProject, 1999-2018
All Rights Reserved.
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100