Microsoft KB Archive/192718

= FIX: RDS Query Times Out After Five Minutes =

Article ID: 192718

Article Last Modified on 5/17/2007

-

APPLIES TO


 * Microsoft Remote Data Services 1.5

-



This article was previously published under Q192718



SYMPTOMS
Remote Data Service (RDS) version 1.5 times out when trying to run queries longer than five minutes. Clients receive the following error message:

Internet Client Error : Request Timeout.



CAUSE
The Wininet.dll has a default timeout of five minutes. RDS 1.5 used this .dll file and its default timeout.



RESOLUTION
This limitation is fixed in RDS 2.0 and later. You may download the latest version of Microsoft Data Access Components, including RDS, from the following Web address:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx

NOTE: RDS 1.5 is no longer available for download.

The RDS.Dataspace and RDS.Datacontrol in release 2.0 and later have a new property Called InternetTimeout, which takes the following range of values:


 * Minimum value of -2,147,483,648 (Times out immediately, any negative times out immediately.)
 * Maximum value of 2,147,483,647 (596 hours or 24 days, never times out.)
 * Value of 0 (will not timeout.)
 * Negative value (will timeout immediately.)



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in RDS 2.0 and later.



Steps to Reproduce Behavior
To reproduce the problem create a Visual Basic ActiveX .dll that is installed on the server and runs under RDS from a Visual Basic client application.

This example has a method called WaitForAllotedtime, which takes an input parameter amounting to the delay that you need to create a long running query.

Creating the ActiveX DLL
 Start a new project in Visual Basic and select "ActiveX DLL". Class1 is created by default. From the Project menu, select Project1 Properties. Change the Project name to RDSTimeOutTestObj and the Project Description to RDS Time Out Test Object. Click OK to close the Project Properties dialog box. Select Class1 in your Project Window and press F4 to view the Properties. Change the Instancing property of Class1 to "5 MultiUse".  Paste the following code into the General Declarations section of Class1: Option Explicit Const SUCCESS = 999 Public Function WaitForAllotedtime(ByVal WaitTime As Integer) As _ Integer Pause (WaitTime) 'Introduce a delay simulating a long running query WaitForAllotedtime = SUCCESS End Function

Sub Pause(ByVal nSecond As Single) Dim t0 As Single t0 = Timer Do While Timer - t0 < nSecond ' This loop introduces the delay of Dim dummy As Integer          ' nSecond using the Timer function. dummy = DoEvents If Timer < t0 Then t0 = t0 - CLng(24) * CLng(60) * CLng(60) End If Loop End Sub  Save the project.</li> From the File menu, click "Make RDSTimeOutTestObj.dll". You are now finished creating your ActiveX .dll project.

</li></ol>

Creating the Visual Basic Test Client
<ol> Test the ActiveX .dll project by creating another Visual Basic Standard .exe project as a client.</li> From the File menu, click New Project, and then select Standard .exe project. Form1 is created by default.</li> From the Project menu, select references and add a reference to the Microsoft Remote Data Services 2.0 Library.</li> Place a Command button, named Command1, on Form1.</li>  Paste the following code into the General Declarations section of Form1: Private Sub Command1_Click Dim rs As New RDS.DataSpace Dim obj As Object Dim i As Integer rs.InternetTimeout = 305000  ' This is in milliseconds. Set obj = rs.CreateObject("RDSTimeOutTestObj.Class1", _   "http:// ") i = obj.WaitForAllotedTime(301)'301 seconds, cross the 5 min barrier MsgBox i  ' Should get 999 indicating success. End Sub </li></ol>

NOTE: is the name of your Internet Information Server (IIS) server, which hosts the business object.

Registering the ActiveX .dll to Run on RDS
<ol> If you are not developing on your IIS server, you need to manually copy over the .dll to the IIS server and manually register it using Regsvr32.exe. Also check to make sure the RDSTimeOutTestObj business object is correctly registered on your IIS/RDS server. To see if the component is correctly registered, look in the registry by running "regedit" from the Run menu. The components are under the HKEY_CLASSES_ROOT key in alphabetical order.</li>  Make sure your createable object has launch rights on your server. This can be done by taking the following lines and saving them in a file with a .reg extension and double-clicking the file to merge the information into the registry. You can also do this manually with Regedit.exe: REGEDIT4 ;This entry should be on one line [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC \Parameters\ADCLaunch\RDSTimeOutTestObj.Class1] </li></ol>

Testing the Application
<ol> Run the Visual Basic client.</li> Click the Command1 button.</li> You should see a message box that displays 999, which indicates that the long running query has executed successfully without creating the following error:

Internet Client Error : Request Timeout.

</li> To check whether the InternetTimeOut setting works you can set the InternetTimeOut value to something less than 301000 millisecond to get the error.</li></ol>

<div class="references_section">