Article ID: 907264 - View products that this article applies to.
Bug #: 245183 (SQLBUDT)
Consider the following scenario. A large enterprise application uses Microsoft SQL Server. The application is in a high-stress scenario. When the application tries to access a SQL Server database by using the Microsoft OLE DB Provider for SQL Server (SQLOLEDB),you may receive one or more of the following error messages:
General Network Error
SQL Server Does Not Exist Or Access Denied
This issue occurs when a large enterprise application in a high-stress scenario runs many queries on OLE DB sessions or on ActiveX Data Objects (ADO) connections that use SQLOLEDB.
For example, the following behavior may occur:
When a large enterprise application is in a high-stress scenario, running many of these new SQL queries creates many corresponding non-pooled implicit connections. Therefore, you may receive "General Network Error" error messages.
You may receive these error messages because one or more of the following conditions are true:
To work around this issue, use one of the following methods:
For more information about implicit connections and SQLOLEDB, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/271128/ )Implicit connections created by the SQL Server OLE DB Provider (SQLOLEDB) are not pooled
194979For more information about connection pooling, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/194979/ )ADO spawns additional connections to SQL Server
(http://support.microsoft.com/kb/328476/ )Description of TCP/IP settings that you may have to adjust when SQL Server connection pooling is disabled
Article ID: 907264 - Last Review: March 14, 2007 - Revision: 1.2
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Contact us for more help