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

ID: Q219756

The information in this article applies to:
BUG #: 54203 (SQLBUG_70)

SYMPTOMS

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.


STATUS

Microsoft has confirmed this to be a problem in SQL Server version 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server version 7.0. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.


MORE INFORMATION

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.

Additional query words: sql trace hang hangs hung 


Keywords          : kbbug7.00 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: June 8, 1999