You are currently offline, waiting for your internet to reconnect

FIX: Connections to SQL Server May Result in Handle Leak If SQLTRACE Is Enabled

This article was previously published under Q219756
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 54203 (SQLBUG_70)
If you use SQL Server Profiler or the xp_trace_setqueryhistory extended stored procedure to enable SQLTrace, a new connection to SQL Server will result in a memory and handle leak within Sqlservr.exe by Sqltrace.dll.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
If the leak occurs over a period of time, SQL Server may stop responding to new connections or queries.

You may also see one or more of the following errors in the error log:
Error: 17803, Severity: 17, State: 14
Insufficient memory available..
Error: 17803, Severity: 17, State: 17
Insufficient memory available..
Error: 17801, Severity: 17, State: 1
Unknown internal error value..
Error: 17826, Severity: 18, State: 2
Could not set up ListenOn connection '\\.\pipe\sql\query'..
Operating system error 1450., Insufficient system resources exist to
complete the requested service.

The actual behavior will depend on what activity is being executed within the server. The memory and handles allocated within Sqltrace.dll will not be cleaned up until SQL Server is shut down and restarted.
sql trace hang hangs hung

Article ID: 219756 - Last Review: 10/14/2013 19:47:14 - Revision: 2.0

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB219756