HTTP clients stop responding after you make only three concurrent HTTP connections to stress test applications in SQL Server Analysis Services SP3 (903005)

SYMPTOMS

In Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3), you make HTTP connections to stress test applications. However, HTTP clients stop responding (hang) after you make only three concurrent connections.

You may experience this issue in the following scenarios:

In production environments
When you use Microsoft Application Center to perform stress testing

This issue occurs when one of the following conditions is true:

You use HTTP to open multiple OLE DB sessions for the same process.
You use a middle-tier component to connect to Analysis Services.

RESOLUTION

To resolve this issue, follow these steps:

Add "Restricted Client=2" to the connection string for Analysis Services.

For example, the following connection string contains "Restricted Client=2":
Data Source=http://localhost;Restricted Client=2;Initial Catalog=FoodMart 2000;Provider=msolap.2;
Install SQL Server 2000 Service Pack 4 (SP4). For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

MORE INFORMATION

The steps that are listed in the "Resolution" section resolve the issue in which HTTP clients stop responding. However, you will not experience improved performance. This behavior is by design. When you specify the "Restricted Client=2" connection string property, you serialize calls to the WinInet API. You also increase the number of limitations of the Wininet.dll library. You use the Wininet.dll library on the client for HTTP connections.