Configure Web Service CLient Timeout via Config File??

[Crash]

VS 2003
..NET 1.x
Windows 2000 SP4

Hi all,

We recently migrated a data center containing several database and ASP
web service servers. We have a Windows Forms application that runs on
200+ user desktops and it does all database access through a web
service middle tier running in the new data center location.

After the migration most everyone is working fine however one of our
"far away and really remote" locations has started experiencing
lockups and timeouts when communicating with the web service tier. We
will NOT be able to back out of the data center migration and there is
little to no chance that the "really remote" location will be upgraded
to a higher bandwidth connection.

This leaves me with the option of increasing web request timeouts from
the client side. Is there any way to increase a web service request
timeout via a configuration file? If not from the config file is
there anything I can do at the machine.config or even OS level that
would extend the timeouts on the web service requests??

 

[Egghead]

you mean that when you set the app with timeout set to over one hour (inside
the code), and it works fine.
It is not timeout. It is the same problem as your IE lockup after few mins
waiting. If your app runs over around 8 mins without reply it, your client
will just sit there.

 

[Crash]

you mean that when you set the app with timeout set to over one hour (inside
the code), and it works fine.

Huhh?? - We haven't set any timeouts in code...

In my case an employee was terminted under rather hostile
circumstances and I have inherited an application. We are unsure if I
have the latest version of the source code - or if the source code
was tampered with; so I would rather NOT make changes to the code...

Sooo I would like to increase the web service timeouts via a config
file if possible. Do you know of any way to do this?

 

[Egghead]

If that is the default, you should have more than enough.
Anyway, you should make a test app and test it. I believe it will change
nothing even you set the timeout inside your code to 1 hour.