CODEWITHSUNDEEP
c#web-servicesdebugging
Cody
Cody

Reputation: 401

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

I have been testing a vendors webservice for the past month which was working fine. Then one day it started timing out. After setting the timeout property higher I started getting this response back. I was told that no changes were made on their side and that they could not recreate my issue. I was also told that there was no changes made on our network.

I have been searching around for a day or two here but have proved fruitless on my attempts to get closer to a solution. At this point I truly believe it is on their end but my question is, is there a way to prove more definitively where the issue is short of having their server logs? The other wrinkle here which makes me feel it is their problem is that they have another webservice which I can still get valid responses back from.

I use fiddler2 but I don't know if I can test a webservice with the request builder, it doesn't seem to work.

My setup is as follows I am using visual studio 2008 C# asp.net project with a web reference to this service.

Thank you very much in advance for your help

Upvotes: 1

Views: 3649

Answers (1)

Jon Skeet
Jon Skeet

Reputation: 1503429

Use Wireshark to get network traces. It'll be tricky to diagnose if you're using HTTPS, but it's lower-level than Fiddler, which means they won't be able to claim that the proxying is causing problems.

Basically, you need to make sure that the request really is being sent, and that you're not getting a response back in time.

Upvotes: 2

Related Questions