If it is a HTTP Time-Out, using "<httpRuntime executionTimeout" should be
enough. So, make sure it is not a DataBase Time-Out.
BTW, if your ASP.NET Web-App is within the same Server where the WebService
is..., probably you should't use WebServices, just call a .DLL Class-Library
with Business and Data Access Components accesing the DataBase. You will
achive a much more better performance. In most scenarios It does not make
sense to use WebServices (HTTP) within the same Server, you get a lot of
latency because of HTTP... (take into account I do not know your scenario,
but I see that you need a better performance system).
Anyway, for that scenario (10 minutes loading an ASP.NET page), may be you
should think about having a async. environment, or a 'client-polling' system.
An ASP.NET loading for 10 minutes doesn't make sense to me...

Signature
CESAR DE LA TORRE
Software Architect
[Microsoft MVP - XML Web Services]
[MCSE] [MCT]
Renacimiento
[Microsoft GOLD Certified Partner]
> Hi,
> My ASP.NET application calls a web service (in the same project) that
[quoted text clipped - 9 lines]
>
> Dorte
S.M. Altaf [MVP] - 21 Oct 2005 21:32 GMT
I agree with the latter part of cesar's comments, but I think that often, web services are necessary in certain scenarios, especially when you want a loosely coupled architecture in place which can be scaled to other clients at a later point in time.
-Altaf [MVP]
--------------------------------------------------------------------------------
All that glitters has a high refractive index.
www.mendhak.com
If it is a HTTP Time-Out, using "<httpRuntime executionTimeout" should be
enough. So, make sure it is not a DataBase Time-Out.
BTW, if your ASP.NET Web-App is within the same Server where the WebService
is..., probably you should't use WebServices, just call a .DLL Class-Library
with Business and Data Access Components accesing the DataBase. You will
achive a much more better performance. In most scenarios It does not make
sense to use WebServices (HTTP) within the same Server, you get a lot of
latency because of HTTP... (take into account I do not know your scenario,
but I see that you need a better performance system).
Anyway, for that scenario (10 minutes loading an ASP.NET page), may be you
should think about having a async. environment, or a 'client-polling' system.
An ASP.NET loading for 10 minutes doesn't make sense to me...
--
CESAR DE LA TORRE
Software Architect
[Microsoft MVP - XML Web Services]
[MCSE] [MCT]
Renacimiento
[Microsoft GOLD Certified Partner]
"Dorte" wrote:
> Hi,
> My ASP.NET application calls a web service (in the same project) that
> queries a SQL server by using a data adapter to fill a dataset. The
> dataadapter may fill more than one dataset to build the resulting dataset.
> This can take several minutes (I think up to approximately 10 minutes) before
> a result set is ready. The result set is displayed in a datagrid. It works ok
> in VS.NET but when the project is deployed, the time consuming queries
> generate the following error "Request timed out"
> I have set the httpRuntime executionTimeout="900" in the web.config but it
> does not make any change.
> Does anyone know how to solve this problem? Thanks in advance for any replies.
>
> Dorte