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

June 19, 2015

I have sometimes seen WCF services that times out. The easiest way to fix it is to increase the timeout value within the config file. Here is an example of this can be done.

  1. <binding name="WSHttpBinding_ILoanService" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00">  
  2. </binding>


Okay, so there are four different timeouts - what do they mean.

I was running an application using Visual Studio and for not so apparent reason the web service was not working. Since I was debugging the web site connecting to a web service within visual studio - it was not apparent as to why it was failing. When I started debugging the web service, I figured it resulting in an error - Memory gates checking failed because the free memory (296964096 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..

August 25, 2013

Sometimes, when we connect to web services from within Visual Studio, I have noticed the error - 407 Error: Proxy Authentication Required while running webservice. This error is not anything to do code but basically that the system cannot connect to the remote WCF web service. To debug this issue, I usually try to navigate to the web service in the web browser - Internet Explorer. If the service is available then metadata page for the web service will appear. If not, the system cannot access the service. If it can connect via Internet Explorer, then add the following section in the web.config file. This setting allows Visual Studio to use the proxy setting from Internet Explorer to make any internet connection including connecting to the service.

Reference: Shahed Kazi at AspNetify.com