PRB: Error 17882 "Error Accepting Connection Request via Net-Library 'SSNETLIB'. Execution Continuing" When You Connect to SQL Server (811887)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

SYMPTOMS

When applications try to connect to SQL Server, the computer that is running SQL Server may not respond.

You may see the following error in the SQL Server error log:
2003-01-01 10:45:19.84 server Error: 17882, Severity: 18, State: 1
2002-01-01 10:45:19.84 server Error accepting connection request via Net-Library 'SSNETLIB'. Execution continuing..

CAUSE

This behavior may occur when you use system stored procedures that allow Automation objects and you use these system stored procedures in Transact-SQL batches, stored procedures, or triggers.

WORKAROUND

To work around this problem, explicitly call the sp_OADestroy stored procedure to destroy an Automation object.

MORE INFORMATION

When you use the sp_OACreate stored procedure to create an Automation object, the object is created in the SQL Server address space. If sp_OADestroy stored procedure is not used to successfully destroy the OLE object , the memory that the object is using may not be cleared. The sp_OAMethod, sp_OAGetProperty, and sp_OASetPropertyDue stored procedures may also contribute to memory leaks. Therefore, the SQL Server may run out of memory and stop responding. For additional information about how to monitor SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

224587 HOW TO: Troubleshoot Application Performance with SQL Server

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

282229 FIX: SP_OA Procedures Leak Memory and Cause Various Errors

298475 HOW TO: Troubleshoot Application Performance Issues

Modification Type:MajorLast Reviewed:9/16/2003
Keywords:kbProgramming kbSQLProg kberrmsg kbprb KB811887 kbAudDeveloper
©2003 Microsoft Corporation. All rights reserved.