1

We have ASP.NET Web Service running on IIS6 that has long-running methods (processing takes about 5 minutes).

When we call the web service from Win 2003 Server, our client gets HTTP 503 error after waiting for the response for couple of minutes. So we never get the response data back to the client, even though, the call is actually completed on the server (our application logging shows that the whole method gets executed). So the execution on the server side is not stopped, client just stops waiting for the response.

However, when we call the same method with the same parameters and the same client from Win XP workstation, everything works as expected and we don't get any HTTP errors.

Does anyone got any ideas why this error happens only when calling from Server OS? Is there some registry or other setting where you can control how long OS waits for HTTP responses?

Mikko Leinonen
  • 11
  • 2
  • Look at the eventlog for the specific error. 503 is just a generic HTTP response error. – leppie Feb 02 '11 at 08:16
  • Client side: No eventlog errors. Server side: No eventlog errors, except the one that we put as debug to tell us that the server side process is completed. I know that 503 is generic HTTP response, but we never get it when calling from XP machine so it would seem that its not caused by the server (though HTTP errors should always come from server, right?). – Mikko Leinonen Feb 03 '11 at 07:01

0 Answers0