Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

First, note that it is inefficient to use XML to transfer large amounts of data because of the overhead of XML.

There are three actions you can take to change the Web service timeout values:

1. On the machine where SAS BI Web Services for .NET is installed, check the responseDeadlockInterval property of the <processModel> element in the machine.config file. (Search the %systemroot%\Microsoft.NET\Framework\v1.*\CONFIG\ folder for your machine.config file, where v1.* is the version of the .NET Framework that you are attempting to configure.) In ASP.NET 1.0, the value of this property is 10 minutes; in ASP.NET 1.1, the value is 3 minutes. Increase this value appropriately, depending on how long you expect your Web service requests to take.

2. Modify the executionTimeout attribute of the httpRuntime element in the web.config file for the SASWS Web application. The httpRuntime element might not exist in your web.config file, so you might need to add it as a child of the system.web element. The following code is an example of the httpRuntime element:

      <httpRuntime
        executionTimeout="300"
        maxRequestLength="10000"/>
   

3. If you are developing a Web service client using Microsoft .NET, there is also a timeout specified in the Web service proxy class. When creating an instance of your Web service proxy class, be sure to specify an appropriate value for the proxyClass.Timeout property. This value is measured in milliseconds, so a value of 1200000 would create a timeout of 20 minutes.

Operating System and Release Information