I have a timeout issue with a long running web service, and I can't figure
out where
the timeout value is coming from. In the client I end up getting the
following exception:

The underlying connection was closed: An unexpected error occurred on a
receive.
  at
System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest
request)
  at
System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
request)
  at
Microsoft.Web.Services2.WebServicesClientProtocol.GetWebResponse(WebRequest
request)
  at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
  at ExchangeClient.localhost.DataExchangeWse.Import(String UserName,
String Password, DataType Type, ImportOperation Op) in C:\Documents and
Settings\gallen\ArrAy\HC\src\Voyager\Subprojects\DataExchange\ExchangeClient\Web
References\localhost\Reference.vb:line 42
  at ExchangeClient.ThreadData.RunThread() in C:\Documents and
Settings\gallen\ArrAy\HC\src\Voyager\Subprojects\DataExchange\ExchangeClient\MainFrm.vb:line
520

If I run the both web service and the client on my local machine, it runs in
about
700 seconds without issue.

When I try to run using a web service on a different machine, I get the
exception above.  I have
checked both the machine.config and the web.config on the web service
machine, and
can't find any timeout setting that would be causing this to happen.

This happens *every* time at about 600 seconds, so I suspect there is a
timeout value
somewhere that I should be setting.  I've tried everything I can think of,
and executionTimeout is
set in the web.config:

     <httpRuntime executionTimeout="900" />

This is of course more than the 600 seconds I am seeing when the timeout
happens (at
around 600 seconds).

I also compared my local machine.config and web.config with the remote ones,
but
they don't appear to have significant differences.

Can anyone help?

Thanks,

-- Greg Allen