BUG: An HTTP connection to an instance of SQL Server 2005 may time out

If you use HTTP to connect to an instance of Microsoft SQL Server 2005 on a computer that is running the original release version of Microsoft Windows Server 2003, the HTTP connection may time out and may end unexpectedly. This problem occurs after the instance of SQL Server 2005 receives the SQL Server data that you sent as an HTTP request over the HTTP connection.

The timer in Http.sys is the kernel mode driver that handles HTTP requests in Windows Server 2003. This timer is not reset correctly after the instance of SQL Server receives the data as an HTTP request. Because the default connection time-out period is set to 120 seconds, the HTTP connection times out and ends if SQL Server 2005 takes more than 120 seconds to process the client request and to send the processing results as an HTTP response to the client.

To work around this problem, you must increase the connection time-out value of the Web sites on the computer that is running Microsoft Internet Information Services (IIS). For example, if IIS is installed on the computer that is running your instance of SQL Server 2005, follow these steps on the computer to increase the connection time-out value:

1. Click Start, click Run, type inetmgr, and then click OK.
2. In the left pane of the Internet Information Services (IIS) Manager window, expand Internet Information Services, expand ComputerName, and then expand Web Sites.
3. Right-click Default Web Site, and then click Properties.
4. In the Default Web Site Properties dialog box, click the Web Site tab.
5. Under the Connections section, type the new connection time-out value in the Connection timeout box.
6. Click Apply, and then click OK.

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

The following list describes some situations where this problem may occur:

• A SOAP/HTTP client sends a SOAP request to the instance of SQL Server 2005 over HTTP to start a stored procedure. The stored procedure may require more than 120 seconds to run successfully.
• A SOAP/HTTP client sends a batch that contains Transact-SQL to the instance of SQL Server 2005. The batch may require more than 120 seconds to process the batch.