Sample Timeouts

The sample is timing out for me when I run a simple search.  Any ideas   I've tried passing proxy server info and adding a custom GetWebRequest with no keepalives.

System.Net.WebException: The operation has timed-out
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at WindowsSearchFormVB.MSNSearch.MSNSearchService.Search(SearchRequest Request)
at WindowsSearchFormVB.WindowsSearchForm.frmSearchSample.btnSearch_Click(Object sender, EventArgs e)


 




Answer this question

Sample Timeouts

  • Trevor Damster

    Very impressive.  Yes the timeout issues seem to be fixed and the application functions as intended.

    Thanks!

  • Mok4402

    Seth, WHY are the sample applications TIMING OUT It's been that way for nearly 24 hours

    I've added my AppID value...

  • JDiego

    Yeah me too... C'mon Seth whats up brah We're dyin to mash this in with our G & Y stuff.

  • Aleks Spacca

    Erin, thanks for the status update. It's blazin fast now.

  • Jose Valim

    Yeah me too Rohan... let me guess, line 38 of reference.cs

    Hopefully it will be available soon. I was hoping to spend my lunch getting to know the api a little better.

  • Christian38

    Agreed.  I got Google and Yahoo's working fine from behind our proxy server.  Not sure what the scoop is.  It appears that others who are using PHP-Soap directly aren't having problems.  Any insight Seth

  • AYK

    I've been running into the exact same problem, both with the samples in the SDK as well as with my own code. At first I thought it might be because of an incorrect AppID, but the timeout occurs whether I specify an AppID or not.

    Probably best to just wait this out.

  • Julian Keith Loren MCSD MCAD

    Hmm, I set it to 1 result and 0 offset and I get the same thing.

  • ahives

    Hey folks --

    With respect to potential firewall issues, I've hoisted the following comments from our documentation:

    If MSN Search Web Service is being called from behind a proxy server that enforces limits on SOAP packet size, you may experience issues with sending and receiving large SOAP packets. For example, a call to the MSN Search Web Service that returns a large number of results may result in a large SOAP packet being sent. You may need to bypass the proxy, set the SOAP packet size limit very high, or limit the amount of data you are requesting.

    With respect to the latency issues folks are seeing, we're looking into these now.  As soon as I hear anything, I'll post what I've learned on the forum.

    Seth...



  • Chris Richner

    I've tried both (Corporporate behind and in front of firewall + I tried at home last night) Port Of Dreams... being that it's an open service shouldn't this be communitating over port 80 anyway

  • Rulery

    The timeout issues should have been resolved Friday evening.  Please let us know if you are still experiencing them.



  • jchan

    Are you guys trying to connect to the web service from behind a firewall or on a corporate network   I was thinking my problem had something to do with that.  But if you guys aren't, then that isn't it.

  • Sample Timeouts