>>>There're some property values of the SoapClient after the error:
>>>
>>>FaultCode: Client
>>>FaultString: Client: Connection failure.
>>>Detail: Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x800A14B4 - Client:Connection failure. HRESULT=0x800A14B4
>>
>>If you look at your Internet download process, if visually you can, you'll see that it downloads a lot. I have a visual cable modem at home and as soon as the download starts the lights are flashing pretty fast until the error. This is always at 30 seconds. So, something is forcing the error to kick in at 30 seconds even if the download is not terminated.
>>
>>Basically, if the download is 27 seconds, it'll work. Increase the number of records and it'll timeout. This is ridiculous.
>
>Maybe this timeout is on the Web Services site not on the SoapClient?

Interesting, I always assumed that was control locally. As, from a browser, if a page takes longer than 30 seconds to download, it is not cut. I assumed it was the same here. So, that would mean, it would react differently from a Web Service than from a browser. Anyone know if that setting should be applied inside the Web Service or from the HTTP server?