Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: ConnectionWrite Error When You Use Lightweight Pooling
Article ID: 303120 - View products that this article applies to.
This article was previously published under Q303120
When you get a long-running result set from a SQL Server 2000 instance configured to run with lightweight pooling (fiber mode), you may see one of the following errors:
General network error. Net-Library error 10054: ConnectionWrite(send()).
Possible network error: Error in sending out-of-band data to SQL Server. General network error. Check your documentation. Net-Library error 10054: ConnectionWrite (send()).
To resolve this problem, obtain the latest service pack for SQL Server 2000, the latest service pack for MDAC 2.6, or the hotfix referenced below.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
290211For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
(http://support.microsoft.com/kb/300635/EN-US/ )INFO: How to Obtain the Latest MDAC 2.6 Service Pack
HotfixNOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 2.
The English version of this fix should have the following file attributes or later:
Date File name Size Version Platform -------------------------------------------------------------- 19-JUN-2001 Ssnetlib.dll 86,078 2000.80.304.0 x86
This problem does not occur if you run SQL Server without lightweight pooling.
In most cases, you do not receive a benefit from setting lightweight pooling on; for more information, see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/319942/EN-US/ )HOW TO: Determine Proper SQL Server Configuration Settings
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2 and MDAC 2.6 Service Pack 2.