FIX: Connection Failure With VIA/GigaNet Protocol (811274)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions) SP3

SYMPTOMS

When you use the Virtual Interface Architecture (VIA) protocol with the GigaNet System Area Network (SAN) (generally referred to as VIA/GigaNet protocol), after a period of time all new VIA/GigaNet protocol connections to SQL Server fail. When you examine the SQL Server 2000 error log, you notice the following error log messages:
server Error: 17882, Severity: 18, State: 1
server Error accepting connection request via Net-Library 'SSNETLIB'. Execution continuing...
server Error: 17059, Severity: 18, State: 0
server Operating system error 0: The operation completed successfully...
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

CAUSE

The connection failures are caused by an internal memory leak of VIA/GigaNet connection objects in SQL Server. When approximately 290,000 connection objects are leaked, no more connection objects can be created in the heap where connection objects are stored.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version        Size    File name     Platform
   ----------------------------------------------------------------
   26-Feb-2003  03:40  2000.80.777.0  29,244  Dbmslpcn.dll    x86
   26-Feb-2003  03:40  2000.80.777.0  29,244  Ssmslpcn.dll    x86
   26-Feb-2003  03:37  2000.80.777.0  82,492  Ssnetlib.dll    x86

WORKAROUND

To avoid this problem, periodically stop and restart SQL Server. This recycles the SQL Server process and clears all the leaked connection objects.

STATUS

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

MORE INFORMATION

Each VIA/GigaNet connection that you open and close leaks one internal connection object. If you attach a debugger to the SQL Server process, you notice that one heap in the process has 64 extents. This is the maximum number of extents that a single NT heap allows. Therefore, when the last extent is exhausted, subsequent allocations from the heap fail.
Modification Type:MajorLast Reviewed:4/7/2006
Keywords:kbQFE KBHotfixServer kbSQLServ2000sp3fix KB811274 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.