Showing posts with label WCF. Show all posts
Showing posts with label WCF. Show all posts

Thursday, January 12, 2017

There was no endpoint listening at (url) that could accept the message

                                                               Recently I got this exception .When I was trying to call a WCF service hosted in a new server from a Web application in my local. I got the error below

There was no endpoint listening at http://localhost:[number]/XXXXX.svc that could accept the

message. This is often caused by an incorrect address or SOAP action. See InnerException,

if present, for more details.


Initially i thought that some configuration went wrong .After investigation i found that we need to disable the default proxy.I have  added below config settings  in  the Web.config of service host project. After that everything worked perfectly !!!

<system.net>
    <defaultproxy enabled="false">
    </defaultproxy>
</system.net>


Friday, March 18, 2016

Memory gates checking failed because the free memory (373817344 bytes) is less than 5% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.

         I had this problem when i am trying to run the WCF services project in local . It mostly happens when the  Memory gates checking failed due to the free memory  is less than  of total memory




        As a outcome, the service will not be available for taking the  incoming requests. To fix this issue, either reduce the load on the machine or set the zero value for minFreeMemoryPercentageToActivateService in the web.config as specified below


 
  

Wednesday, September 21, 2011

The maximum message size quota for incoming messages , has been exceeded. To increase the quota,..WCF exception

 

                                        Recently i got this exception when i work with WCF service. One of the Web Method returns heavy data.It is not an issue. The problem hear is  maxReceivedMessageSize is exceeded .         
The Default value of maxReceivedMessageSize is "65536". We can change this value upto "2147483647".I have increased the size of maxBufferSize,maxReceivedMessageSize  in Web.config file (Binding section).

The problem got resolved .

 

maxWCF

 

Note: Don’t copy all the code .Only change the maxBufferSize,maxReceivedMessageSize  as I specified in below .

<binding name="BasicHttpBinding_Service1" closeTimeout="00:01:00"
                    openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
                    allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
                    maxBufferSize="2147483647" maxBufferPoolSize="524288" maxReceivedMessageSize="2147483647"
                    messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
                    useDefaultWebProxy="true">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                        maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <security mode="None">
                        <transport clientCredentialType="None" proxyCredentialType="None"
                            realm="" />
                        <message clientCredentialType="UserName" algorithmSuite="Default" />
                    </security>
                </binding>

Happy coding ..