This article has been archived. It is offered "as is" and will no longer be updated.
If you call a Web service method, and if the method call takes a long time to return (typically more than 100 seconds), the client application may receive the following exception:
The underlying connection was closed
This may occur if all the following conditions are true:
You call the Web service method from a computer that is running Windows 98 Second Edition or Windows Millennium Edition.
You use a client application to set the Web service proxy timeout value to infinite.
The client application is developed by using Microsoft .NET Framework.
The network monitor trace shows that the client has closed the connection by using TCP FIN.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File Name Platform ------------------------------------------------------------------------- 26-Apr-2003 04:12 1.0.3705.425 196,608 Aspnet_isapi.dll x86 26-Apr-2003 04:06 4,169 Aspnet_perf.h 26-Apr-2003 04:12 513,302 Aspnet_perf.ini 26-Apr-2003 04:12 510,714 Aspnet_perf2.ini 26-Apr-2003 04:12 1.0.3705.425 24,576 Aspnet_regiis.exe x86 26-Apr-2003 04:12 1.0.3705.425 28,672 Aspnet_wp.exe x86 26-Apr-2003 03:36 1.0.3705.425 69,632 Corperfmonext.dll x86 26-Apr-2003 03:34 1.0.3705.425 303,104 Mscorjit.dll x86 26-Apr-2003 14:29 1.0.3705.425 1,953,792 Mscorlib.dll x86 24-Apr-2003 18:40 10,284 Mscorlib.ldo 26-Apr-2003 03:35 1.0.3705.425 2,269,184 Mscorsvr.dll x86 26-Apr-2003 03:35 1.0.3705.425 2,269,184 Mscorwks.dll x86 01-Aug-2002 21:38 15 Smartnav.htm 17-Oct-2002 17:55 8,728 Smartnav.js 26-Apr-2003 14:29 1.0.3705.425 1,191,936 System.web.dll x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The default proxy timeout value for the client is 100 seconds. You can modify the proxy timeout value by using the timeout property of the proxy as follows:
webserver.Service1 ws = new webserver.Service1();ws.Timeout = System.Threading.Timeout.Infinite;